I put a new build on the web page today, one that I made completely on a Linux machine. However, I was not able to find a free Windows box on which to try it out. If someone has the time, please give it a try. By "cross-compiler" , I mean the same MinGW-modified GCC that we normally use on Windows, but built on Linux instead.
It is likely incredibly buggy, being the first one made this way, but hey, it's a start. If this works, we can start automated builds soon.
Bob
Bob, Before I have a look at the cross-compiled build I would like to get preferences.xml sorted out. I installed Inkscape040106 this morning. Actually the program says it is 040105 but I'm more concerned about preferences.xml at this stage. When I change preferences.xml Inkscape does not pick the changes up. It appears to be ignoring preference.xml when it is changed and overwriting it when the program installs.
Am I doing something wrong? I am sinply modifying preferences.xml with NotePad and saving. Can't get much simpler than that. Win200 system
vellum
either when sthe pis ----- Original Message ----- From: "Bob Jamison" <rjamison@...73...> To: "Inkscape Devel List" inkscape-devel@lists.sourceforge.net Sent: Wednesday, January 07, 2004 11:32 AM Subject: [Inkscape-devel] Win32 cross-compiled build
I put a new build on the web page today, one that I made completely on a Linux machine. However, I was not able to find a free Windows box on which to try it out. If someone has the time, please give it a
try.
By "cross-compiler" , I mean the same MinGW-modified GCC that we normally use on Windows, but built on Linux instead.
It is likely incredibly buggy, being the first one made this way, but hey, it's a start. If this works, we can start automated builds soon.
Bob
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
vellum wrote:
Am I doing something wrong? I am sinply modifying preferences.xml with NotePad and saving. Can't get much simpler than that. Win200 system
Actually, you can get a *lot* simpler.
Notepad on WinNT based systems knows many different encodings, including a few different Unicode encodings.
I'd suggest checking the initial bytes of your preferences before and after. Could be UTF-8 BOM hiding in there.
Jon wrote
Actually, you can get a *lot* simpler.
Thanks Jon, but I'm trying to solve this problem.
Notepad on WinNT based systems knows many different encodings, including a few different Unicode encodings.
I'd suggest checking the initial bytes of your preferences before and after. Could be UTF-8 BOM hiding in there.
OK. The preferences.xml file appears to be UTF-8 encoded according to the first line. Whether the modified file is saved as UTF-8 or ANSI (my default Notepad save mode) the following happens.
With Inkscape build 031231 the preferences file is picked up and the preferences are used. With Inkscape build 040106 the preferences file is not picked up.
Swapping preference files does not alter things. I read this as a change in Inkscape and nothing to do with the preferences file.
Can someone help here? For example, Bob, what happened between these two releases?
vellum
vellum wrote:
Bob, Before I have a look at the cross-compiled build I would like to get preferences.xml sorted out. I installed Inkscape040106 this morning. Actually the program says it is 040105 but I'm more concerned about preferences.xml at this stage. When I change preferences.xml Inkscape does not pick the changes up. It appears to be ignoring preference.xml when it is changed and overwriting it when the program installs.
Am I doing something wrong? I am sinply modifying preferences.xml with NotePad and saving. Can't get much simpler than that. Win200 system
vellum
Well, I changed nothing between the two. I have noticed, however, that upon startup, the Win32 version creates an "Inkscape" subdirectory, and places a preferences.xml in there. Is this the one you are editing?
As far as encoding, I don't think libxml2 would reject your file if it is merely the difference between ascii and utf-8. The only times I have had trouble with a parser rejecting a file, is when the specified encoding is not available.
If people really want preferences.xml to be saved in a place specified by the registry, I would assume the program would:
1) Look in the registry-defined location for preferences.xml 2) If it isn't found there, then look in the /inkscape subdir 3) If found, keep using that location for the duration of the session. Done 4) If not found, create a new one 5) If the location is defined in the registry put it there 6) If not defined put it in the /inkscape subdir. 7) Keep using -that- location for the duration of the session. Done
I might be able to test this out this evening when I can use a Windows box again.
Bob
Bob Jamison wrote:
As far as encoding, I don't think libxml2 would reject your file if it is merely the difference between ascii and utf-8. The only times I have had trouble with a parser rejecting a file, is when the specified encoding is not available.
It'd be best to check.
Versions 1.x of J Clark's expat all would die if a file included a UTF-8 BOM at the begining. Given all the polish and test cases it had, it probably used to be a very rare thing. Also, I've seen lots of people run into problems with WinNT notepad's transparent handling of encodings.
By now, though, the parsers have probably all been fixed.
On Tue, 6 Jan 2004, Bob Jamison wrote:
I put a new build on the web page today, one that I made completely on a Linux machine. However, I was not able to find a free Windows box on which to try it out. If someone has the time, please give it a try. By "cross-compiler" , I mean the same MinGW-modified GCC that we normally use on Windows, but built on Linux instead.
It is likely incredibly buggy, being the first one made this way, but hey, it's a start. If this works, we can start automated builds soon.
Wow, this is *very* cool to hear. It will be wonderful to get to a day where we can generate a bulk of the distros from a single machine.
I wonder if crosscompiling for OSX on PPC is feasible?
Bryce
MenTaLguY wrote:
On Wed, 2004-01-07 at 16:22, Bryce Harrington wrote:
I wonder if crosscompiling for OSX on PPC is feasible?
That would require a Linux build of Apple's gcc fork, at least. I don't know how portable their changes are.
-mental
Might be fun to investigate. With Gcc, you can make a cross-compiler for almost any architecture. But for any target, you still need the base runtime lib. Basically their C lib, plus kernel hooks. MinGW supply their Win32 mapping and C runtime on their site, already built and ready to go.
If Darwin also has such a lib... -cool-.
Btw. Notice I said "MinGW supply....." Aggregate plural instead of aggregate singular. I must be turning British.
Bob
participants (5)
-
Bob Jamison -
Bryce Harrington -
Jon A. Cruz -
MenTaLguY -
vellum