Hi everybody,
I tried the Mac OS X aqua adventure again and am running into strange =20=
occurancies:
(Mac OS X 10.4.11, PPC)
./autogen results in
>> I am testing that you have the required versions of autoconf,
>> automake, glib-gettextize and intltoolize. This test is not =20
>> foolproof and
>> if anything goes wrong, there may be guidance in the file HACKING.txt
>>
>> checking for autoconf >=3D 2.52 ... yes (version 2.59)
>> checking for automake >=3D 1.10 ... Too old (found version 1.6.3)!
>> checking for glib-gettextize >=3D 2.0.0 ...
>> You must have glib-gettextize installed to compile Inkscape.
>> glib-gettextize is part of glib-2.0, so you should already
>> have it. Make sure it is in your PATH.
>> checking for intltool >=3D 0.17 ...
>> You must have intltool installed to compile Inkscape.
>> Get the latest version from
>> ftp://ftp.gnome.org/pub/GNOME/sources/intltool/
Intltool should be new enough:
>> port installed intltool
>> The following ports are currently installed:
>> intltool @0.40.6-0 (active)
=85 so should be automake:
>> bub$ port installed automake
>> The following ports are currently installed:
>> automake @1.11-0 (active)
Hints appreciated=85
Greetings,
Wolf
Hi everybody,<div><br></div><div>I tried the Mac OS X aqua adventure =
again and am running into strange occurancies:</div><div>(Mac OS X =
10.4.11, PPC)</div><div><br></div><div>./autogen results =
in</div><div><br></div><div><div><blockquote type=3D"cite"><blockquote =
type=3D"cite"><div><i>I am testing that you have the required versions =
of autoconf,</i></div><div><i>automake, glib-gettextize and intltoolize. =
This test is not foolproof and</i></div><div><i>if anything goes wrong, =
there may be guidance in the file =
HACKING.txt</i></div><div><i><br></i></div><div><i>checking for autoconf =
>=3D 2.52 ... yes (version 2.59)</i></div><div><i>checking for =
automake >=3D 1.10 ... Too old (found version =
1.6.3)!</i></div><div><i>checking for glib-gettextize >=3D 2.0.0 =
... </i></div><div><i> You must have glib-gettextize =
installed to compile =
Inkscape.</i></div><div><i> glib-gettextize is part of =
glib-2.0, so you should already</i></div><div><i> have it. =
Make sure it is in your PATH.</i></div><div><i>checking for intltool =
>=3D 0.17 ... </i></div><div><i> You must have =
intltool installed to compile Inkscape.</i></div><div><i> Get =
the latest version from</i></div><div><i> <a =
href=3D"ftp://ftp.gnome.org/pub/GNOME/sources/intltool/">ftp://ftp.gnome.o=
rg/pub/GNOME/sources/intltool/</a></i></div></blockquote></blockquote></di=
v><div><br></div><div><br></div><div>Intltool should be new =
enough:</div><div><br></div><div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><div>port installed =
intltool</div><div>The following ports are currently =
installed:</div><div> intltool @0.40.6-0 =
(active)</div></blockquote></blockquote></div><div><br></div></div><div>=85=
so should be automake:</div><div><br></div><div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><div><div>bub$ port installed =
automake</div><div>The following ports are currently =
installed:</div><div> automake @1.11-0 =
(active)</div></div></blockquote></blockquote></div></div><div><br></div><=
div>Hints =
appreciated=85</div><div><br></div><div><div>Greetings,</div><div><br></di=
v><div>Wolf</div></div><div><br></div></div></body></html>=
Re: Inkscape-devel - 0.47 - Mac OS X aqua by ~suv on
2009-11-21T12:59:49+00:00
On 21/11/09 14:42, Wolf Drechsel wrote:
> I tried the Mac OS X aqua adventure again and am running into strange
> occurancies:
> (Mac OS X 10.4.11, PPC)
> =
> ./autogen results in
> =
>>> /I am testing that you have the required versions of autoconf,/
>>> /automake, glib-gettextize and intltoolize. This test is not
>>> foolproof and/
>>> /if anything goes wrong, there may be guidance in the file HACKING.txt/
>>> /
>>> /
>>> /checking for autoconf >=3D 2.52 ... yes (version 2.59)/
>>> /checking for automake >=3D 1.10 ... Too old (found version 1.6.3)!/
>>> /checking for glib-gettextize >=3D 2.0.0 ... /
>>> / You must have glib-gettextize installed to compile Inkscape./
>>> / glib-gettextize is part of glib-2.0, so you should already/
>>> / have it. Make sure it is in your PATH./
>>> /checking for intltool >=3D 0.17 ... /
>>> / You must have intltool installed to compile Inkscape./
>>> / Get the latest version from/
>>> / ftp://ftp.gnome.org/pub/GNOME/sources/intltool//
> =
> =
> Intltool should be new enough:
> =
>>> port installed intltool
>>> The following ports are currently installed:
>>> intltool @0.40.6-0 (active)
> =
> =85 so should be automake:
> =
>>> bub$ port installed automake
>>> The following ports are currently installed:
>>> automake @1.11-0 (active)
> =
> Hints appreciated=85
apply the patch from the macports Inkscape-devel port to autogen.sh as I
described in my recent message:
<http://article.gmane.org/gmane.comp.graphics.inkscape.devel/32091>
reason: recently built MacPorts trees on OS X only have automake 1.11,
whereas the Inkscape autogen.sh script checks for automake 1.10 only.
The patch adds the test for automake 1.11 to autogen.sh.
hth, ~suv
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Re: Inkscape-devel - 0.47 - Mac OS X aqua by Wolf Drechsel on
2009-11-21T13:23:44+00:00
> apply the patch from the macports Inkscape-devel port to autogen.sh =
> as I
> described in my recent message:
> <http://article.gmane.org/gmane.comp.graphics.inkscape.devel/32091>
>
> reason: recently built MacPorts trees on OS X only have automake 1.11,
> whereas the Inkscape autogen.sh script checks for automake 1.10 only.
> The patch adds the test for automake 1.11 to autogen.sh.
Hi ~suv,
such I tried - but didnt do a thing=85 )-;
> /usr/bin/automake: automake (GNU automake) 1.6.3
> no automake-1.7 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin / =
> opt/local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
> tools-version.sh: line 30: automake-1.7: command not found
> no automake-1.8 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin / =
> opt/local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
> tools-version.sh: line 30: automake-1.8: command not found
> no automake-1.9 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin / =
> opt/local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
> tools-version.sh: line 30: automake-1.9: command not found
> /usr/bin/aclocal: aclocal (GNU automake) 1.6.3
> no aclocal-1.7 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
> tools-version.sh: line 30: aclocal-1.7: command not found
> no aclocal-1.8 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
> tools-version.sh: line 30: aclocal-1.8: command not found
> no aclocal-1.9 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
> tools-version.sh: line 30: aclocal-1.9: command not found
> no intltoolize in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
> tools-version.sh: line 30: intltoolize: command not found
> no gettextize in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
> tools-version.sh: line 30: gettextize: command not found
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =
> =3D=3D=3D=3D=3D=3D=3D
>
> I am testing that you have the required versions of autoconf,
> automake, glib-gettextize and intltoolize. This test is not =
> foolproof and
> if anything goes wrong, there may be guidance in the file HACKING.txt
>
> checking for autoconf >=3D 2.52 ... yes (version 2.59)
> checking for automake >=3D 1.10 ... Too old (found version 1.6.3)!
> checking for glib-gettextize >=3D 2.0.0 ...
> You must have glib-gettextize installed to compile Inkscape.
> glib-gettextize is part of glib-2.0, so you should already
> have it. Make sure it is in your PATH.
> checking for intltool >=3D 0.17 ...
> You must have intltool installed to compile Inkscape.
> Get the latest version from
> ftp://ftp.gnome.org/pub/GNOME/sources/intltool/
Greetings,
Wolf
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Re: Inkscape-devel - 0.47 - Mac OS X aqua by ~suv on
2009-11-21T13:51:15+00:00
On 21/11/09 15:22, Wolf Drechsel wrote:
>> apply the patch from the macports Inkscape-devel port to autogen.sh =
>> as I
>> described in my recent message:
>> <http://article.gmane.org/gmane.comp.graphics.inkscape.devel/32091>
>>
>> reason: recently built MacPorts trees on OS X only have automake 1.11,
>> whereas the Inkscape autogen.sh script checks for automake 1.10 only.
>> The patch adds the test for automake 1.11 to autogen.sh.
> =
> Hi ~suv,
> =
> such I tried - but didnt do a thing=85 )-;
> =
>> /usr/bin/automake: automake (GNU automake) 1.6.3
>> no automake-1.7 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin / =
>> opt/local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
>> tools-version.sh: line 30: automake-1.7: command not found
>> no automake-1.8 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin / =
>> opt/local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
>> tools-version.sh: line 30: automake-1.8: command not found
>> no automake-1.9 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin / =
>> opt/local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
>> tools-version.sh: line 30: automake-1.9: command not found
>> /usr/bin/aclocal: aclocal (GNU automake) 1.6.3
>> no aclocal-1.7 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
>> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
>> tools-version.sh: line 30: aclocal-1.7: command not found
>> no aclocal-1.8 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
>> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
>> tools-version.sh: line 30: aclocal-1.8: command not found
>> no aclocal-1.9 in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
>> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
>> tools-version.sh: line 30: aclocal-1.9: command not found
>> no intltoolize in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
>> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
>> tools-version.sh: line 30: intltoolize: command not found
>> no gettextize in /bin /sbin /usr/bin /usr/sbin /usr/X11R6/bin /opt/ =
>> local/var/macports/software/automake/1.11-0 /opt/local/share: ./ =
>> tools-version.sh: line 30: gettextize: command not found
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =
1) How did you apply the patch exactly?
2) Your $PATH certainly does look strange to me - it can't find any
recently installed tools in MacPorts because you haven't added it
correctly in your PATH.
Why did you modify the PATH to only include
'/opt/local/var/macports/software/automake/1.11-0' and did you check if
that directory even contains the automake binary you are looking for (it
doesn't in my macports tree...)?
It is really best to use the scripts in 'packaging/macosx' to run
autogen.sh and configure with the correct environment set up (after
patching autogen.sh).
start again, cleanup any remnants from the failed autogen.sh runs with
'./delautogen.sh' or 'make distclean', then 'cd packaging/macosx' and
run './osx-build.sh a' and if this succeeds './osx-build.sh c' to
configure your source tree.
~suv
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Re: Inkscape-devel - 0.47 - Mac OS X aqua by ~suv on
2009-11-21T14:00:04+00:00
attaching the patched version (from SVN r22576) of autogen.sh
save it to 'inkscape/src' and use 'chmod 755 autogen.sh' to make it
executable. the 'cd packaging/macosx' and run './osx-build.sh a'
hth, ~suv
Re: Inkscape-devel - 0.47 - Mac OS X aqua by Wolf Drechsel on
2009-11-21T15:24:52+00:00
Hello ~suv, good fellow=85
o.k. - I went back to the very beginning, using a freshly unpacked =
sources directory.
I copied your autogen.sh to the sources root directory (I dont think =
it will work in the src dir) and did chmod 755.
Then I tried both (following my records from the first inkscape aqua =
building session):
Moved to the source root dir, did:
> export CC=3D"ccache gcc"
> export CXX=3D"ccache g++"
> export LIBPREFIX=3D"/opt/local"
> export CPATH=3D"$LIBPREFIX/include"
> export CPPFLAGS=3D"-I$LIBPREFIX/include"
> export LDFLAGS=3D"-L$LIBPREFIX/lib"
> export CFLAGS=3D"-O3 -Wall"
> export CXXFLAGS=3D"$CFLAGS"
> export PATH=3D/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
>
> sudo ./autogen.sh
ending up with:
> dsl01:~/Desktop/inkscape-0.47 bub$ sudo ./autogen.sh
> ./autogen.sh: line 27: ./tools-version.sh: No such file or directory
>
> I am testing that you have the required versions of autoconf,
> automake, glib-gettextize and intltoolize. This test is not =
> foolproof and
> if anything goes wrong, there may be guidance in the file HACKING.txt
>
> checking for autoconf >=3D 2.52 ... yes (version 2.59)
> checking for automake >=3D 1.10 ... Too old (found version 1.6.3)!
> checking for glib-gettextize >=3D 2.0.0 ...
> You must have glib-gettextize installed to compile Inkscape.
> glib-gettextize is part of glib-2.0, so you should already
> have it. Make sure it is in your PATH.
> checking for intltool >=3D 0.17 ...
> You must have intltool installed to compile Inkscape.
> Get the latest version from
> ftp://ftp.gnome.org/pub/GNOME/sources/intltool/
>
> Please install/upgrade the missing tools and call me again.
On a second go, I tried:
Moving to the packaging/macosx dir, pasting the export commands from =
above, and then doing sudo ./osx-build.sh a leads to the same result.
> 2) Your $PATH certainly does look strange to me - it can't find any
> recently installed tools in MacPorts because you haven't added it
> correctly in your PATH.
> Why did you modify the PATH to only include
> '/opt/local/var/macports/software/automake/1.11-0' and did you =
> check if
> that directory even contains the automake binary you are looking =
> for (it
> doesn't in my macports tree...)?
Automake can be found here:
>> /opt/local/bin/automake
>> /opt/local/share/doc/automake
>> /opt/local/var/macports/distfiles/automake
>> /opt/local/var/macports/receipts/automake
>> /opt/local/var/macports/software/automake
>> /opt/local/var/macports/software/automake/1.11-0/opt/local/bin/ =
>> automake
>> /opt/local/var/macports/software/automake/1.11-0/opt/local/share/ =
>> doc/automake
>> /opt/local/var/macports/sources/rsync.macports.org/release/ports/ =
>> devel/automake
>> f
and intltool here:
>> /opt/local/share/intltool
>> /opt/local/var/macports/distfiles/intltool
>> /opt/local/var/macports/receipts/intltool
>> /opt/local/var/macports/software/intltool
>> /opt/local/var/macports/software/intltool/0.40.6-0/opt/local/share/ =
>> intltool
>> /opt/local/var/macports/sources/rsync.macports.org/release/ports/ =
>> textproc/intltool
glib-2.0 here:
>> /opt/local/include/glib-2.0
>> /opt/local/lib/glib-2.0
>> /opt/local/share/glib-2.0
>> /opt/local/var/macports/software/glib2/2.20.5-0+darwin/opt/local/ =
>> include/glib-2.0
>> /opt/local/var/macports/software/glib2/2.20.5-0+darwin/opt/local/ =
>> lib/glib-2.0
>> /opt/local/var/macports/software/glib2/2.20.5-0+darwin/opt/local/ =
>> share/glib-2.0
I was trying to include these things into the path by adding the =
directories after amother colon - seemed not to be working=85 - Can you =
give me the correct settings?
> It is really best to use the scripts in 'packaging/macosx' to run
> autogen.sh and configure with the correct environment set up (after
> patching autogen.sh).
>
> start again, cleanup any remnants from the failed autogen.sh runs with
> './delautogen.sh' or 'make distclean', then 'cd packaging/macosx' and
> run './osx-build.sh a' and if this succeeds './osx-build.sh c' to
> configure your source tree.
o.k. - I'm trying to work on that=85
Greetings,
Wolf
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Re: Inkscape-devel - 0.47 - Mac OS X aqua by ~suv on
2009-11-21T16:01:31+00:00
On 21/11/09 17:23, Wolf Drechsel wrote:
> o.k. - I went back to the very beginning, using a freshly unpacked =
> sources directory.
> =
> I copied your autogen.sh to the sources root directory (I dont think =
> it will work in the src dir) and did chmod 755.
Sorry, I made a mistake - you are correct, it belongs in the inkscape
root directory of the unpacked sources.
> Then I tried both (following my records from the first inkscape aqua =
> building session):
> =
> Moved to the source root dir, did:
> =
> =
>> export CC=3D"ccache gcc"
>> export CXX=3D"ccache g++"
>> export LIBPREFIX=3D"/opt/local"
>> export CPATH=3D"$LIBPREFIX/include"
>> export CPPFLAGS=3D"-I$LIBPREFIX/include"
>> export LDFLAGS=3D"-L$LIBPREFIX/lib"
>> export CFLAGS=3D"-O3 -Wall"
>> export CXXFLAGS=3D"$CFLAGS"
>> export PATH=3D/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
>>
>> sudo ./autogen.sh
Your $PATH here is wrong.
I assume you copied that from the Wiki page where it is quoted in the
instructions to install a second MacPorts tree (i.e. when configuring,
building and installing 'MacPorts-1.x.x'), but *only* for that.
Afterwards you *need* to have '/opt/local/bin' (or wherever your current
MacPorts tree is installed for the native build) as the first directory
of your path, otherwise you can't configure and build inkscape using the
dependencies and buildtools installed in MacPorts. Usually a correct
installation of MacPorts either takes care of that by adding it to your
'~/.profile' or by informing you that you have to update your $PATH and
$MANPATH settings in your shell startup file (be it '~/.profile' or
'~/.bash-profile').
Can you open a new terminal window, type 'env' and paste the output into
your next reply?
> On a second go, I tried:
> =
> Moving to the packaging/macosx dir, pasting the export commands from =
> above, and then doing sudo ./osx-build.sh a leads to the same result.
I guess that's because the shell script inherits the wrong $PATH if you
explicitly restrict it before running osx-build.sh.
Note: you need the other explicit environment settings *only* if you try
to use 'autogen.sh' and 'configure' directly instead of using the
osx-build script (which sets those variables for you). i.e. no need to
set them separately if you plan to use the packaging scripts ;-)
>> 2) Your $PATH certainly does look strange to me - it can't find any
>> recently installed tools in MacPorts because you haven't added it
>> correctly in your PATH.
> I was trying to include these things into the path by adding the =
> directories after amother colon - seemed not to be working=85 - Can you =
> give me the correct settings?
A correct installation of MacPorts takes care of that - there's no need
to add additional subdirectories of '/opt/local' to your $PATH - see above.
>> It is really best to use the scripts in 'packaging/macosx' to run
>> autogen.sh and configure with the correct environment set up (after
>> patching autogen.sh).
>>
>> start again, cleanup any remnants from the failed autogen.sh runs with
>> './delautogen.sh' or 'make distclean', then 'cd packaging/macosx' and
>> run './osx-build.sh a' and if this succeeds './osx-build.sh c' to
>> configure your source tree.
> =
> o.k. - I'm trying to work on that=85
I just tried that again with the new 0.47 source package and it ran
autogen.sh and configure without errors. (Haven't yet run
'./osx-build.sh b' to build it).
~suv
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Re: Inkscape-devel - 0.47 - Mac OS X aqua by ~suv on
2009-11-22T05:16:22+00:00
On 21/11/09 18:00, ~suv wrote:
> On 21/11/09 17:23, Wolf Drechsel wrote:
>> o.k. - I went back to the very beginning, using a freshly unpacked
>> sources directory.
>>
>> I copied your autogen.sh to the sources root directory (I dont think
>> it will work in the src dir) and did chmod 755.
>
> Sorry, I made a mistake - you are correct, it belongs in the inkscape
> root directory of the unpacked sources.
Puzzled by the seemingly missing 'autogen.sh' I went searching for
answers and discovered another mistake I made... *blush*
Looking at the autogen.sh file itself rather than patching it reveals:
(...)
# If you are compiling from a released tarball you don't need these
# tools and you shouldn't use this script. Just call ./configure
# directly.
(...)
To test this I repeated the now abbreviated 'configure' from before: In
a newly unpacked 0.47 source directory:
$ cd packaging/macosx
$ cp -p osx-build.sh osx-build.sh.orig
$ vim osx-build.sh # setting prefix for MacPorts
$ ./osx-build.sh c
and it ran through without errors, returning this configuration:
> Configuration:
>
> Source code location: .
> Destination path prefix: /Volumes/blue/src/Inkscape/0-47/inkscape-0.47/packaging/macosx/../../Build
> Compiler: g++
> CPPFLAGS: -Wall -Wformat -Wformat-security -W -D-FORTIFY-SOURCE=2 -I/Volumes/blue/mp/include
> CXXFLAGS: -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -O3 -Wall
> CFLAGS: -Wno-pointer-sign -O3 -Wall
> LDFLAGS: -L/Volumes/blue/mp/lib
>
> Use Xft font database: yes
> Use gnome-vfs: yes
> Use openoffice files: yes
> Use MMX optimizations: no
> Use relocation support: no
> Internal Python: skipped
> Internal Perl: skipped
> Enable LittleCms: yes
> Enable Poppler-Cairo: yes
> ImageMagick Magick++: yes
> Libwpg: yes
so you don't need 'autogen.sh' when building from a dist tar file, I
didn't know that. But this is the reason why it isn't included (and
wasn't in the earlier prerelease source tarballs nor in the 0.46 release
source tarball).
~suv (feeling bad :( because my instructions again turned out to be wrong)
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Re: Inkscape-devel - 0.47 - Mac OS X aqua by Wolf Drechsel on
2009-11-22T15:13:33+00:00
> # If you are compiling from a released tarball you don't need these
> # tools and you shouldn't use this script. Just call ./configure
> # directly.
> (...)
>
> To test this I repeated the now abbreviated 'configure' from =
> before: In
> a newly unpacked 0.47 source directory:
>
> $ cd packaging/macosx
> $ cp -p osx-build.sh osx-build.sh.orig
> $ vim osx-build.sh # setting prefix for MacPorts
> $ ./osx-build.sh c
o.k. - here we go. I didnt do something else - just unpacked the =
tarball and threw it onto the desktop.
Than:
> $ cd packaging/macosx
> $ cp -p osx-build.sh osx-build.sh.orig
> $ vim osx-build.sh # setting prefix for MacPorts
Hm. I found this in the instructions:
# CONFFLAGS=3D"o.k. - tried that, came out with:
> Configuration:
>
> Source code location: .
> Destination path prefix: /Users/bub/Desktop/inkscape-0.47/ =
> packaging/macosx/../../Build
> Compiler: ccache g++
> CPPFLAGS: -Wall -Wformat -Wformat-security - =
> W -D-FORTIFY-SOURCE=3D2 -I/opt/local/include
> CXXFLAGS: -Wpointer-arith -Wcast-align - =
> Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter - =
> O3 -Wall
> CFLAGS: -Wno-pointer-sign -O3 -Wall
> LDFLAGS: -L/opt/local/lib
>
> Use Xft font database: yes
> Use gnome-vfs: yes
> Use openoffice files: yes
> Use MMX optimizations: no
> Use relocation support: no
> Internal Python: skipped
> Internal Perl: skipped
> Enable LittleCms: yes
> Enable Poppler-Cairo: yes
> ImageMagick Magick++: no
> Libwpg: yes
>
> head: ../../.svn/entries: No such file or directory
I guess the last linie is about the thing with macports prefix?
And now - how do I go on?
Greetings,
Wolf
PS.: Please dont care about some errata - they are the machines, not =
us=85 ((-;
I'm extremely gradeful you are spending such a lot of time on my =
strange stuff=85
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Re: Inkscape-devel - 0.47 - Mac OS X aqua by ~suv on
2009-11-22T15:58:59+00:00
On 22/11/09 17:10, Wolf Drechsel wrote:
> o.k. - here we go. I didnt do something else - just unpacked the =
> tarball and threw it onto the desktop.
> =
> Than:
> =
>> $ cd packaging/macosx
>> $ cp -p osx-build.sh osx-build.sh.orig
>> $ vim osx-build.sh # setting prefix for MacPorts
> =
> Hm. I found this in the instructions:
> =
> # CONFFLAGS=3D"'/Volumes/blue/mp', you can see a different path when comparing my
configuration to yours. ]
Basically it is the point where you make any necessary changes to
'osx-build.sh' ('vim' is a command line editor, you probably prefer to
use textedit with 'open -a textedit osx-build.sh'), be it to set the
correct path to your MacPorts tree or to change configuration options
(like disabling 'osxapp' by removing 'same tree - AFAIK that's not recommended).
If you use a different MacPorts tree to build the Aqua version, just
edit 'LIBPREFIX' on line 26 of 'osx-build.sh' to use a different path.
On the wiki page describing your first build experience in September you
mention '/opt/local-native' - this is what needs to be set as LIBPREFIX
if it is where the dependencies of inkscape are installed as native
versions without X11 (all the gtk, glib, pango, cairo, fontconfig stuff...)
>> $ ./osx-build.sh c
> =
> o.k. - tried that, came out with:
> =
>> Configuration:
>>
>> Source code location: .
>> Destination path prefix: /Users/bub/Desktop/inkscape-0.47/packa=
ging/macosx/../../Build
>> Compiler: ccache g++
>> CPPFLAGS: -Wall -Wformat -Wformat-security -W -D=
-FORTIFY-SOURCE=3D2 -I/opt/local/include
>> CXXFLAGS: -Wpointer-arith -Wcast-align -Wsign-co=
mpare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -O3 -Wall
>> CFLAGS: -Wno-pointer-sign -O3 -Wall
>> LDFLAGS: -L/opt/local/lib
>>
>> Use Xft font database: yes
>> Use gnome-vfs: yes
>> Use openoffice files: yes
>> Use MMX optimizations: no
>> Use relocation support: no
>> Internal Python: skipped
>> Internal Perl: skipped
>> Enable LittleCms: yes
>> Enable Poppler-Cairo: yes
>> ImageMagick Magick++: no
>> Libwpg: yes
>>
>> head: ../../.svn/entries: No such file or directory
looks ok to me (if '/opt/local' is what you need for the Aqua version).
Else - change 'LIBPREFIX' and rerun './osx-build.sh c'
> I guess the last linie is about the thing with macports prefix?
I get the line about the svn entries too, but I think that's because it
still tries to retrieve the SVN revision number and fails because it
isn't a checkout from the repositories but a release tarball (no
revision number is added to the version string).
> And now - how do I go on?
the next step: building inkscape with
$ ./osx-build.sh b
and if this succeeds, installing it locally with
$ ./osx-build.sh i
and it should be ready to be used.
~suv
[1] Inkscape 0.46 crash with 'FcStrListCreate'
That crash looks like a known issue to me - I can search the bug
number if needed, the fix could be necessary on two levels.
first try this:
1) clear the user font cache (rm ~/.fontconfig/*)
2) restart Inkscape
if that doesn't fix it, you have to edit the font configuration file
inside the 0.46 app bundle, I'll post a follow-up with instructions
and the link to the corresponding bug report.
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel