On Wed, 9 Nov 2005, jiho wrote:
> On 9 nov. 05, at 01:13, Michael Wybrow wrote:
>> There were a couple of problems with this package:
>> - It was missing all the translation files. This is probably due to a
>> bug in your version of gcc which causes the configure test for a valid
>> "dgettext" function to fail, even though it exists on OS X. (I've had
>> the same problem. A workaround is to set "ac_cv_lib_intl_dgettext=yes"
> My version of gcc is gcc 3.3 from os X on Tiger. How can I check if the
> nightlies I built have the same problem?
The nightlies have the problem if they are missing the
Inkscape.app/Contents/Resources/locale directory or it is empty.
> And then how to I set "ac_cv_lib_intl_dgettext=yes"? is it in the makefile?
> as an environment variable? maybe it should be in the wiki somewhere (like in
> troubleshooting section)?
You can just set it as an environment variable, prior to running
configure. I'll add a comment about this soon.
> About package size: my packages are 24.8 MB and the resulting inkscape is 80
> MB and I am apparently missing some files. Yours are 14 MB and resulting
> Inkscape is 32 MB and is complete. what am I doing wrong???
You're not doing anything wrong. It just that mine are stripped, and
yours are not (i.e., the libraries still include all the debugging
>> - It did not have the correct paths set inside the executable, which
>> causes problems like some of the icons not displaying in some cases.
>> This is because when builing the OS X package, Inkscape should be
>> configured with the "--enable-osxapp" option. I've documented this
>> in the OS X package build script as well as in the wiki instructions.
> I wasn't aware of the option sorry. Once again all seemed fine to me but I
> guess it is because I only tested it on my system.
> By the way, with previous builds (the only I did not do myself) I remarked
> that the tutorials were not accessible. Is it part of the same problem? can
> you access tutorials in my builds? I can in the pre2-2 I downloaded (I assume
> it is yours).
Yes, this would be the cause of the tutorials not being accessible. No, I
couldn't access them in your build.
> As to the wiki I'll rather put the option directly next to configure because
> the way it is now will probably lead people to configure make and make
> install before seeing it and they will have to redo the whole thing. In
> addition I guess that everybody compiling on os X will probably want his
Sure, feel free to change this. But also note that anyone building on OS
X who is not planning to make bundles (i.e., anyone doing Inkscape
development) won't want to use this option.
> Additional note about python:
> As I understand it, python is shipped with mac os X, even without the
> developers packaged installed. does somebody knows if pyXML is somewhere
> inside this?
> fink apparently has a package pyxml for different versions of python but it
> requires to install python from fink which is a waste of space and compile
> time. in addition, know that there is an Inkscape package it would be great
> to be able to use it completely without fink.
> My idea behind this is that, as effects are enabled by default now, as most
> of them require pyxml, as mac os X has python and as mac users are lazy and
> want ready to use stuff, would it be possible to use os x python, or provide
> them with a package or... whatever.
I haven't looked at python or getting the effects working without fink.
Please feel free explore what needs to be done to get this working nicely.