I'm updating the downloads.php page in preparation for the testing effort. What is the proper link(s) that we should be pointing to for the Windows builds now?
Bryce
Hello.
On Sat, 2004-06-19 at 13:42, Bryce Harrington wrote:
I'm updating the downloads.php page in preparation for the testing effort. What is the proper link(s) that we should be pointing to for the Windows builds now? Bryce
I don't know about Bob's, but here is my server: http://cortijodelrio.net/~inkscape/
Maybe including both? (If Bob agrees, of course)
But the builds have been broken since the 14th. Today's error is: In file included from verbs.h:13, from interface.h:18, from desktop.cpp:57: require-config.h:2:3: #error "Must #include config.h (ifdef HAVE_CONFIG_H) before anything else." make[1]: *** [desktop.o] Error 1
It went further when require-config.h was commented out in verbs.h, but I really don't know what's the right thing to do here. I hope Bob or somebody could take care of that.
And as for Linux, I get: make[1]: *** No rule to make target `libnrtype/FontInstance.h', needed by `distdir'. Stop.
The autobuilding process is still on three times a day: at @000, at @333, and at @666 (Internet Time). So, as soon as it is fixed the zip's will be there.
Daniel Díaz yosoy@...31...
I fixed the CVS version so that it is building again. Occasionally, if there are missing dependencies, it is necessary to run:
perl mkfiles.pl and perl mkdep.pl
....and if it works nicely, commit the make.* files that are generated.
This is because during development, files are added and deleted from the build. The recent tectonic plate change in libnrtype ;-) for Pangoization is a good example. The Win32 Makefile.mingw files are not part of the Gnuish automake/autoconf world, so those commands need to be re-run occasionally for us to sync with Unix.
By the way, it is almost time to assemble the Gtk/Glib libraries again into a package, as Tor Lillqvist has recently posted Gtk2.4. We are currently at 2.2.4. This should of course be after 0.39, but we will finally be able to benefit from newer libraries and the new file dialogs. And maybe the "focus out of bounds" bug will finally go away.
Daniel Díaz wrote:
But the builds have been broken since the 14th. Today's error is: In file included from verbs.h:13, from interface.h:18, from desktop.cpp:57: require-config.h:2:3: #error "Must #include config.h (ifdef HAVE_CONFIG_H) before anything else." make[1]: *** [desktop.o] Error 1
It went further when require-config.h was commented out in verbs.h, but I really don't know what's the right thing to do here. I hope Bob or somebody could take care of that.
And as for Linux, I get: make[1]: *** No rule to make target `libnrtype/FontInstance.h', needed by `distdir'. Stop.
The autobuilding process is still on three times a day: at @000, at @333, and at @666 (Internet Time). So, as soon as it is fixed the zip's will be there.
Daniel Díaz yosoy@...31...
Ok, I fixed it -again- , and now it should be building again. I put an autobuild on the server. I do have a couple of questions, though.
What is the purpose of require-config.h? Config.h seems to be always required, so maybe we can instead get rid of the #ifdef HAVE_CONFIG_H switches?
Where did src/config.h.win32 come from? I thought it was deleted. I someone intending on building Inkscape with MSVC?
Ok, that was 4. ;-)
Bob
On Sun, Jun 20, 2004 at 11:37:08AM -0500, Bob Jamison wrote:
What is the purpose of require-config.h?
The verb enum in verbs.h contains
... #ifdef HAVE_GTK_WINDOW_FULLSCREEN SP_VERB_FULLSCREEN, #endif /* HAVE_GTK_WINDOW_FULLSCREEN */ SP_VERB_VIEW_NEW, ...
so the value of e.g. SP_VERB_VIEW_NEW depends on whether HAVE_GTK_WINDOW_FULLSCREEN is defined.
It could be bad if some translation units #included verbs.h without previously including config.h (which defines HAVE_GTK_WINDOW_FULLSCREEN iff appropriate). There are two possible fixes for this:
i) have verbs.h #include <config.h> (perhaps conditionally on HAVE_CONFIG_H, see below).
ii) have verbs.h #include <require-config.h>, which should force a compilation error iff <config.h> hasn't already been included.
Autoconf documentation (*see (autoconf)Configuration Headers) recommends that config.h be included before any other headers. If we heed this advice, then we should use approach (ii).
However, the reasons for its recommendations are not as important for C++ as for C. E.g. our config.h should never contain `#define const', as basic support for `const' (e.g. recognizing `T' and `T const' as distinct types) is fairly important for a C++ compiler.
Even so, the consistency of (ii) (having the config.h definitions present for all header files) does have some appeal.
The advantage of (i) over (ii) is having one less header file: developers don't ask themselves what require-config.h is.
config.h seems to be always required, so maybe we can instead get rid of the #ifdef HAVE_CONFIG_H switches?
Making `#include <config.h>' conditional on HAVE_CONFIG_H allows compiling even if configured without AC_CONFIG_HEADERS, i.e. having -D flags on the command-line instead of creating config.h (see the above-cited section of autoconf documentation). Not a big deal.
Where did src/config.h.win32 come from? I thought it was deleted. I someone intending on building Inkscape with MSVC?
Given that require-config.h triggered a compile error for you, I'm guessing that you're using config.h.win32: the macro tested by require-config.h wasn't present in config.h.win32 until about a day after require-config.h was introduced. Just a guess, I'm not very familiar with inkscape's compilation on windows.
pjrm.
Thanks, I've updated the downloads page with links to both servers, and added a bit more explanatory text.
Thanks to everyone who helped with getting the Windows builds online.
http://inkscape.org/download.php
Bryce
On Sat, 19 Jun 2004, Daniel [ISO-8859-1] D�az wrote:
Hello.
On Sat, 2004-06-19 at 13:42, Bryce Harrington wrote:
I'm updating the downloads.php page in preparation for the testing effort. What is the proper link(s) that we should be pointing to for the Windows builds now? Bryce
I don't know about Bob's, but here is my server: http://cortijodelrio.net/~inkscape/
Maybe including both? (If Bob agrees, of course)
But the builds have been broken since the 14th. Today's error is: In file included from verbs.h:13, from interface.h:18, from desktop.cpp:57: require-config.h:2:3: #error "Must #include config.h (ifdef HAVE_CONFIG_H) before anything else." make[1]: *** [desktop.o] Error 1
It went further when require-config.h was commented out in verbs.h, but I really don't know what's the right thing to do here. I hope Bob or somebody could take care of that.
And as for Linux, I get: make[1]: *** No rule to make target `libnrtype/FontInstance.h', needed by `distdir'. Stop.
The autobuilding process is still on three times a day: at @000, at @333, and at @666 (Internet Time). So, as soon as it is fixed the zip's will be there.
Daniel D�az yosoy@...31...
Daniel has written:
"If you need the Windows version, this is the right place to be. Now, if you already downloaded a ZIP file lately, you can try picking only the inkscape.exe file from the à la carte directory, as that will save you some time."
This works really well. However I have a question which is probably so naive that I'll get shot down for even asking it. On the a la carte page there is an "Inkscape.exe" file at 7.2M and an "Inkscape_stripped.exe" file at 3.2M. I am using the stripped version at present but have used the other version as well. Both appear to work perfectly but the stripped version saves a heap of download time.
What is the difference between them? and are there times when one or the other should be used? If the stripped file can be used all the time then is the other file needed? And should the BEIF refer to the stripped version rather than the unstripped one?
Bobs nightly builds appear to unzip to yield the Inkscape.exe file.
vellum
Hello.
It's really great that this is useful enough to somebody as to ask what are things for.
On Thu, 2004-06-24 at 21:26, vellum wrote:
Daniel has written:
"If you need the Windows version, this is the right place to be. Now, if you already downloaded a ZIP file lately, you can try picking only the inkscape.exe file from the à la carte directory, as that will save you some time."
This works really well. However I have a question which is probably so naive that I'll get shot down for even asking it. On the a la carte page there is an "Inkscape.exe" file at 7.2M and an "Inkscape_stripped.exe" file at 3.2M. I am using the stripped version at present but have used the other version as well. Both appear to work perfectly but the stripped version saves a heap of download time.
What is the difference between them? and are there times when one or the other should be used? If the stripped file can be used all the time then is the other file needed? And should the BEIF refer to the stripped version rather than the unstripped one?
That is true, I added the inkscape_stripped.exe file a couple of days ago and I forgot to add a note about that. It is as new and shiny as the original inkscape.exe file, but this one has no debug symbols therein.
Testers are encouraged to use the unstripped version, as that will ease the debugging process (as per getting a backtrace).
I will now add a note regarding the use of the stripped vs. the unstripped version.
Also, from the next build on (if built, 'cause there is a problem with managed.h), there's gonna be an inkscape_exe.zip which promises to be even smaller.
Bobs nightly builds appear to unzip to yield the Inkscape.exe file.
Yeap. The big ZIP file (Inkscape%y%m%d%H%M.zip) has inkscape.exe and that's it, no stripped version needed.
Now, for the "à la carte" name, what do you all think? I'm not happy with that and I'm open to suggestions. Star points to be awarded to the one that comes up with the best term!
vellum
Greetings!, and thanks for reminding me this.
Daniel Díaz yosoy@...31...
On Thu, 24 Jun 2004, Daniel [ISO-8859-1] D�az wrote:
Now, for the "� la carte" name, what do you all think? I'm not happy with that and I'm open to suggestions. Star points to be awarded to the one that comes up with the best term!
I like it, it immediately clues you in on what it's there for. A downside is that perhaps for non-English (and non-French) speakers, it might not make sense. Maybe 'browsable' would be clearer, but lacks the imagery. ;-)
Bryce
Also, from the next build on (if built, 'cause there is a problem with managed.h), there's gonna be an inkscape_exe.zip which promises to be even smaller.
Bobs nightly builds appear to unzip to yield the Inkscape.exe file.
Yeap. The big ZIP file (Inkscape%y%m%d%H%M.zip) has inkscape.exe and that's it, no stripped version needed.
Instead of Zip have you considered using UPX? http://upx.sourceforge.net/
If you are compressing just an EXE it might produce better results and it produces a binary that can be run without needing to decompress it. I'm sure there must be some speed penalty but for all the times I've used UPX I cant say it is noticable.
Sincerely
Alan Horkan http://advogato.org/person/AlanHorkan/
On Fri, Jun 25, 2004 at 12:26:29PM +1000, vellum wrote:
This works really well. However I have a question which is probably so naive that I'll get shot down for even asking it. On the a la carte page there is an "Inkscape.exe" file at 7.2M and an "Inkscape_stripped.exe" file at 3.2M. I am using the stripped version at present but have used the other version as well. Both appear to work perfectly but the stripped version saves a heap of download time.
What is the difference between them? and are there times when one or the other should be used? If the stripped file can be used all the time then is the other file needed? And should the BEIF refer to the stripped version rather than the unstripped one?
When the binaries are built, the compiler includes all the source symbols so that locations in the binary can be mapped to lines in the source. This is useful for runtime debugging, crash tracing, etc. So if you're not doing those things, go ahead and use the "stripped-of-symbols" binary. :)
I suspect the BEIF is both of them; same binary code, one just lacks the "symbols".
On Thu, 2004-06-24 at 22:26, vellum wrote:
This works really well. However I have a question which is probably so naive that I'll get shot down for even asking it. On the a la carte page there is an "Inkscape.exe" file at 7.2M and an "Inkscape_stripped.exe" file at 3.2M. I am using the stripped version at present but have used the other version as well. Both appear to work perfectly but the stripped version saves a heap of download time.
The stripped version has debugging symbols and stuff removed, so examining it with a debugger or looking at a crash dump isn't very practical.
-mental
participants (8)
-
Alan Horkan -
Bob Jamison -
Bryce Harrington -
Daniel Díaz -
Kees Cook -
MenTaLguY -
Peter Moulder -
vellum