Re: [Inkscape-devel] Tiger packages
(trying to build a Tiger osx package)
I followed the instructions in
http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX
and also installed gtk-clearlooks
I used ./configure --disable-static --enable-shared --prefix=/path/to/build/product --enable-osxap --enable-inkboard. I produced an Inkscape.app but it does not run.
Loading it manually from an xterm gives
macbook:~/inkscape-0.46/packaging/macosx/Inkscape.app/Contents/MacOS duncan$ ./I nkscape
2008-03-29 10:52:34.418 defaults[9262] The domain/default pair of (kCFPreferencesAnyApplication, AppleAquaColorVariant) does not exist 2008-03-29 10:52:34.435 defaults[9263] The domain/default pair of (kCFPreferencesAnyApplication, AppleHighlightColor) d oes not exist
Then it hangs.
Its not clear how to diagnose what the problem is.
Also, the Wiki is written assuming one is using svn. I am using the official 0.46 release tarball, and have no idea whether what I would get by using svn is that or some slightly different version.
I would like to produce an EXACT copy of whatever the "official" release for LEOPARD is (exactly the same options, library dependencies, etc) except built on TIGER.
Is it possible to get the precise build instructions that were used for the Leopard Inskcape.app so I can run them on tiger. (I dont want to make decisions about whether to use e.g. --enable-inkboard )?
One issue I saw when building the .app was
cp: /opt/local/lib/gtk-2.0/2.10.0/loaders/*.so: No such file or directory
I'd try to produce a Tiger universal Inkscape-0.46 dmg for general distribution if the OS X packager no longer has a Tiger/Intel installation to work with, but I need an authoritative recipe for doing it using the official release tarball. I assume using MacPorts is the the way to get the various gtk libraries, so I installed it and the recommended packages, but want to make sure I also produce a dependency-free Inkscape.app that doesnt relay on any external libraries except those that come with Tiger and Tiger/X11 (I will remove Macports as soon as the compilation is successful, as I use Fink).
duncan
-------------- Original message from Bryce Harrington <bryce@...1798...>: --------------
On Wed, Mar 26, 2008 at 03:24:38PM -0400, Jamie Kimberley wrote:
I was building on tiger until a few weeks ago (just got a new macbook). I'll see if I can compile and package the 0.46 code tonight.
If you want to try it yourself the instructions on the wiki using macports are pretty easy to follow. One note not mentioned on the wiki is that you'll need to install the gtk2-clearlooks package before building inkscape from source.
Could you please add this extra note to the wiki. (It's important everyone keep the build directions up to date and as complete as possible, since incorrect build directions can be a show stopper for new devs.)
Thanks, Bryce
simply issue on the command line sudo port install gtk2-clearlooks or add it to the list of other ports that need to be installed.
Sorry, can't give much advice, but good on you for having a go. I know the feeling.
I would recommend putting up anything you learn on the wiki on the way. That's what I've tried to do for Win32.
Hi,
First off, I think Michael (who did the leopard package) was working to get a universal version out for Tiger but did not manage to have it working. I don't know much more. he would.
On 2008-March-29 , at 16:55 , f.duncan.m.haldane@...1154... wrote:
(trying to build a Tiger osx package)
I followed the instructions in
http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX
and also installed gtk-clearlooks
I used ./configure --disable-static --enable-shared --prefix=/path/to/build/ product --enable-osxap --enable-inkboard
it should be --enable-osxapp, with _two_ "p" at the end. maybe that's the issue. But basically, you really should use osx-build.sh if you didn't. It will be easier for you. The info on the wiki just details the process so that you know what's happening behind the scene.
I produced an Inkscape.app but it does not run.
Loading it manually from an xterm gives
macbook:~/inkscape-0.46/packaging/macosx/Inkscape.app/Contents/MacOS duncan$ ./I nkscape
2008-03-29 10:52:34.418 defaults[9262] The domain/default pair of (kCFPreferencesAnyApplication, AppleAquaColorVariant) does not exist 2008-03-29 10:52:34.435 defaults[9263] The domain/default pair of (kCFPreferencesAnyApplication, AppleHighlightColor) d oes not exist
This was fixed in the svn version and I thought it was before 0.46 tarballs were produced. It was apparently not the case so the fix should be backported. The fix was committed at r 17355. Is there anyway for this to make it back in the tarball or should it have to wait for 0.46.1, if it ever happens? Anyway, this should not be a blocker, it would just screw the appearance a bit. To get those message away, just go into os x appaarance settings, change the color to grey and graphite. close the prefs. now go back to them, revert to the state were you were before (or not, if you like graphite ;)) and they're gone.
Then it hangs.
Its not clear how to diagnose what the problem is.
Anything in the system.log (start Console.app in utilities)?
Also, the Wiki is written assuming one is using svn. I am using the official 0.46 release tarball, and have no idea whether what I would get by using svn is that or some slightly different version.
It should be exactly the same. 0.46 is just a snapshot of a particular svn version (more or less).
I would like to produce an EXACT copy of whatever the "official" release for LEOPARD is (exactly the same options, library dependen cies, etc) except built on TIGER.
Is it possible to get the precise build instructions that were used for the Leopard Inskcape.app so I can run them on tiger. (I dont want to make decisions about whether to use e.g. --enable-inkboard )?
Just use the defaults in osx-build.sh i.e. CONFFLAGS="--disable-static --enable-shared --enable-osxapp"
One issue I saw when building the .app was
cp: /opt/local/lib/gtk-2.0/2.10.0/loaders/*.so: No such file or directory
That should not be a problem.
I'd try to produce a Tiger universal Inkscape-0.46 dmg for general distribution if the OS X packager no longer has a Tiger/Intel installation to work with, but I need an authoritative recipe for doing it using the official release tarball. I assume using MacPorts is the the way to get the various gtk libraries, so I installed it and the recommended packages, but want to make sure I also produce a dependency-free Inkscape.app that doesnt relay on any external libraries except those that come with Tiger and Tiger/X11 (I will remove Macports as so on as the compilation is successful, as I use Fink).
Compiling a UB is more tricky. You should really hook up with Michael on this. Basically you must build all libraries in macports as universal (there's a +universal variant of all ports). But to do that you should disable the dependency of gtk on gtk-doc (sudo port edit gtk2 and remove the line about gtk-doc). You should also get a recent version of cairo so that pdf export works nicely: port edit cairo change the version number to 1.5.12 point the address to http://cairographics.org/snapshots/ change the hash checksum to reflect the one of the 1.5.12 version (see http://cairographics.org/snapshots/cairo-1.3.12.tar.gz.sha1) then reinstall cairo in macports
Sorry of this is still not all documented but these changes are recent. And the os x team is reduced. I'll improve the status of the wiki and all in a month or so. Good luck and grab Michael when he's there. _he_ is finished with his PhD ;)
JiHO --- http://jo.irisson.free.fr/
On 30/03/2008, at 4:07 AM, jiho wrote:
First off, I think Michael (who did the leopard package) was working to get a universal version out for Tiger but did not manage to have it working.
I finally got all the dependencies built Universal on 10.4 using macports. Inkscape itself is building as I type this, so I'm very close to having this done.
The CompilingMacOsX page is out of date and I will update it when I have got this process working.
The packaging/macosx scripts in the released 0.46 tarball are also not up to date. As JiHo mentioned, we have both made a few necessary changes to these that will need to be backported to the release branch. I haven't pinged Bryce or anyone about this yet a there is still one more I need to make.
In terms of compiling with Macports, I have been keeping my work on this in the experimental section of the Inkscape repository. (Once I get it all completely working I will start submitting all these changes back to the Macports team.) So, possibly the best way to build an app bundle package of Inkscape from Macports is to checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/experimental/trunk/mjw... to your $HOME/ports, run the command 'portindex' while in the $HOME/ ports directory and then add the line file:///Users/YOURUSERNAME/ports to the /opt/local/etc/macports/sources.conf (before the standard rsync source) and then you should be able to build/update the inkscape dependencies (either Universal or not). I think the current list of dependencies for the app bundle are: gtk2 gtkmm boehmgc libxslt lcms libcroco boost popt gtk2-clearlooks poppler
I'll hopefully make all this very clear on the wiki page in the next few days.
Cheers, Michael
On Sun, Mar 30, 2008 at 05:09:00PM +1100, Michael Wybrow wrote:
I finally got all the dependencies built Universal on 10.4 using macports. Inkscape itself is building as I type this, so I'm very close to having this done.
The CompilingMacOsX page is out of date and I will update it when I have got this process working.
The packaging/macosx scripts in the released 0.46 tarball are also not up to date. As JiHo mentioned, we have both made a few necessary changes to these that will need to be backported to the release branch. I haven't pinged Bryce or anyone about this yet a there is still one more I need to make.
Btw, in case it isn't clear, you an jiho (and anyone else officially on the osx packaging team) should feel free to make any changes needed under the packaging/macosx/ directory. I would also encourage creating a packaging/macosx/patches/ directory for storing inkscape patches necessary for the OSX package, but not yet applied to the tree.
And yes, definitely keep the wiki page up to date with the latest build info. :-)
Bryce
On 30/03/2008, at 7:20 PM, Bryce Harrington wrote:
On Sun, Mar 30, 2008 at 05:09:00PM +1100, Michael Wybrow wrote:
The packaging/macosx scripts in the released 0.46 tarball are also not up to date. As JiHo mentioned, we have both made a few necessary changes to these that will need to be backported to the release branch. I haven't pinged Bryce or anyone about this yet a there is still one more I need to make.
Btw, in case it isn't clear, you an jiho (and anyone else officially on the osx packaging team) should feel free to make any changes needed under the packaging/macosx/ directory.
I don't worry, I'm fearless about that.
The following are the svn commits that should also be applied to the 0.46 release branch to be included in future 0.46.x point releases: Revisions: 17669, 17845, 17866, 17877, 18088 The commit messages for these are included at the end of this email.
I hadn't worried about this till now, because the OSX packages weren't yet completely working, and also because I was the only one building the official packages. FWIW, these patches should bring the packaging/macosx directory on the branch to match the truck version, which I have been using for the process of packaging the official 0.46 Mac packages.
Do I need to create one (or several Launchpad items) for this?
I would also encourage creating a packaging/macosx/patches/ directory for storing inkscape patches necessary for the OSX package, but not yet applied to the tree.
Fortunately, the OSX packages have required alteration of only our own packaging code and Macports Portfiles for building Universal versions of many of the library dependencies, but not the Inkscape 0.46 source code itself.
Cheers, Michael
-----
* packaging/macosx/Resources/themes/Clearlooks-Quicksilver-OSX/gtk-2.0/ pre_gtkrc: Make the highlight colour for the menus be the user's OSX highlight colour, rather than white. * packaging/macosx/osx-app.sh: Include the gtk printbackends in app bundle. * packaging/macosx/ScriptExec/main.c: Update ScriptExec with upstream fixes and changes. X11.app now gets focus if the Inkscape icon is clicked while Inkscape is already open (previously nothing happened). * packaging/macosx/Resources/openDoc: If Inkscape.app is already open and a file is dropped on the Inkscape dock icon, or an Inkscape file is double-clicked in the Finder, that document will now be correctly opened in a new Inkscape window (previously nothing happened). * packaging/macosx/Resources/script: Some minor fixes, plus alert the user about the font cache building time only if ~/.fontconfig/ doesn't exist. * packaging/macosx/Resources/bin/inkscape: Only override the fontconfig configuration on OSX 10.4 or earlier, since the fc-cache behaviour has been corrected on 10.5. * Info.plist.in: Update the copyright dates, and change Inkscape to be an Editor for SVG files, rather than a Viewer as it was previously. * macosx/Resources/bin/inkscape, macosx/Resources/etc/fonts/fonts.conf: Fix fontconfig configuration on machines where Macport's fontconfig is not installed. * packaging/macosx/Resources/openDoc: Fix a bug with the path being set incorrectly when the user opens a second instance of Inkscape by dropping an SVG file on the Dock icon while Inkscape.app is already running. * packaging/macosx/Resources/script: Fx for loading the app bundle on 10.4 systems and prior.
participants (5)
-
unknown＠example.com -
Bryce Harrington -
jiho -
Michael Wybrow -
rygle