Re: [Inkscape-devel] Inkscape 0.44 Hard Freeze
FYI, I just joined inkscape-devel and I'm building on Mac OS X/PPC. There are some redefinitions of preprocessor macros in path-prefix.h that break the build on my platform (CREATE_GRADIENTSDIR, CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
It's pretty clear that most of the paths that now point to locations inside of the application package should probably instead point to the "Application Support" directory in an individual user's home folder for application-generated data. It's less clear to me whether it's a good idea to move a number of the other resource directories outside of the app package simply to be more "mac like" (probably more trouble than it's worth).
I'm planning to spend part of the weekend working on a little extension for some linguistics features (syntax trees), but with builds apparently slightly broken on OS X (one minor change necessary), I'd be more than happy to contribute a patch, work with the Mac module owner, and test.
David Himelright
On Jun 3, 2006, at 10:57 AM, David Vincent Himelright wrote:
FYI, I just joined inkscape-devel and I'm building on Mac OS X/PPC. There are some redefinitions of preprocessor macros in path-prefix.h that break the build on my platform (CREATE_GRADIENTSDIR, CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
Hi, and welcome.
Can you point out which OS X version, etc. you have?
On 03/06/06, Jon A. Cruz <jon@...18...> wrote:
On Jun 3, 2006, at 10:57 AM, David Vincent Himelright wrote:
FYI, I just joined inkscape-devel and I'm building on Mac OS X/PPC. There are some redefinitions of preprocessor macros in path-prefix.h that break the build on my platform (CREATE_GRADIENTSDIR, CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
Can you point out which OS X version, etc. you have?
This is a True Bill, but I thought that it been fixed in svn.
Ben.
I'm building at home on a Tiger (10.4.6) G4 system, and we've got some G5s at work running other versions.
Incidentally, I wish our lab had some Intel Macs so I could offer to patch the packaging scripts for universal binary, but I might be able to find one if I look around.
--David
On Jun 3, 2006, at 2:37 PM, Ben Fowler wrote:
On 03/06/06, Jon A. Cruz <jon@...18...> wrote:
On Jun 3, 2006, at 10:57 AM, David Vincent Himelright wrote:
FYI, I just joined inkscape-devel and I'm building on Mac OS X/PPC. There are some redefinitions of preprocessor macros in path-prefix.h that break the build on my platform (CREATE_GRADIENTSDIR, CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
Can you point out which OS X version, etc. you have?
This is a True Bill, but I thought that it been fixed in svn.
Ben.
On 03/06/06, David Himelright <himelright.2@...1307...> wrote:
I'm building at home on a Tiger (10.4.6) G4 system, and we've got some G5s at work running other versions.
Incidentally, I wish our lab had some Intel Macs so I could offer to patch the packaging scripts for universal binary, but I might be able to find one if I look around.
David, we very definitely need someone to investigate producing a Universal Binary for version 0.44; I cannot see my way to doing anything about it.
You might want to look at http://developer.apple.com/opensource/buildingopensourceuniversal.html which I came acroos about a week ago whilst looking for something else.
On your problem: The page at http://inkscape.modevia.com/doxygen/html/path-prefix_8h-source.php differs from my checked out version.
Are you working from svn or from some tarball?
Ben
On Jun 3, 2006, at 2:37 PM, Ben Fowler wrote:
On 03/06/06, Jon A. Cruz <jon@...18...> wrote:
On Jun 3, 2006, at 10:57 AM, David Vincent Himelright wrote:
FYI, I just joined inkscape-devel and I'm building on Mac OS X/PPC. There are some redefinitions of preprocessor macros in path-prefix.h that break the build on my platform (CREATE_GRADIENTSDIR, CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
Can you point out which OS X version, etc. you have?
This is a True Bill, but I thought that it been fixed in svn.
Hmm, that is odd. I've been working from svn, hacked path-prefix.h up a few weeks ago. I'm thinking that the issue was fixed in source control before I even raised the issue. I've nuked the patched version of path-prefix.h and re-checked out from svn (12184), now rebuilding from source, and it looks like the defines are all in place now.
Re: building universal binaries - I certainly can cross-compile on a PPC system. The step I'd need to take first though would be to completely isolate my build system - including dependencies. I'm currently building support libraries with fink-unstable and while that takes a lot of the work out of patching and configuring dependencies, it also leaves a bit of a mess. I'll see what I can do today about cleaning up, isolating and rebuilding dependencies (gtk, gtkmm, pango) from source outside of the system path.
--David
On Jun 3, 2006, at 3:12 PM, Ben Fowler wrote:
On 03/06/06, David Himelright <himelright.2@...1307...> wrote:
I'm building at home on a Tiger (10.4.6) G4 system, and we've got some G5s at work running other versions.
Incidentally, I wish our lab had some Intel Macs so I could offer to patch the packaging scripts for universal binary, but I might be able to find one if I look around.
David, we very definitely need someone to investigate producing a Universal Binary for version 0.44; I cannot see my way to doing anything about it.
You might want to look at http://developer.apple.com/opensource/buildingopensourceuniversal.html which I came acroos about a week ago whilst looking for something else.
On your problem: The page at http://inkscape.modevia.com/doxygen/html/path-prefix_8h-source.php differs from my checked out version.
Are you working from svn or from some tarball?
Ben
On Jun 3, 2006, at 2:37 PM, Ben Fowler wrote:
On 03/06/06, Jon A. Cruz <jon@...18...> wrote:
On Jun 3, 2006, at 10:57 AM, David Vincent Himelright wrote:
FYI, I just joined inkscape-devel and I'm building on Mac OS X/ PPC. There are some redefinitions of preprocessor macros in path- prefix.h that break the build on my platform (CREATE_GRADIENTSDIR, CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
Can you point out which OS X version, etc. you have?
This is a True Bill, but I thought that it been fixed in svn.
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 03/06/06, David Himelright <himelright.2@...1307...> wrote:
Hmm, that is odd. I've been working from svn, hacked path-prefix.h up a few weeks ago. I'm thinking that the issue was fixed in source control before I even raised the issue. I've nuked the patched version of path-prefix.h and re-checked out from svn (12184), now rebuilding from source, and it looks like the defines are all in place now.
Are you saying that the problem is inactive? You seem to have been doing the same as I, and touch wood, it is O.K. for me.
Re: building universal binaries - I certainly can cross-compile on a PPC system. The step I'd need to take first though would be to completely isolate my build system - including dependencies. I'm currently building support libraries with fink-unstable and while that takes a lot of the work out of patching and configuring dependencies, it also leaves a bit of a mess. I'll see what I can do today about cleaning up, isolating and rebuilding dependencies (gtk, gtkmm, pango) from source outside of the system path.
There was something on the list about two weeks ago, and whilst I haven't built on Tiger since then, I beleive that the ;standard methods' are working.
Ben.
On Jun 3, 2006, at 3:12 PM, Ben Fowler wrote:
On 03/06/06, David Himelright <himelright.2@...1307...> wrote:
I'm building at home on a Tiger (10.4.6) G4 system, and we've got some G5s at work running other versions.
Incidentally, I wish our lab had some Intel Macs so I could offer to patch the packaging scripts for universal binary, but I might be able to find one if I look around.
David, we very definitely need someone to investigate producing a Universal Binary for version 0.44; I cannot see my way to doing anything about it.
You might want to look at http://developer.apple.com/opensource/buildingopensourceuniversal.html which I came acroos about a week ago whilst looking for something else.
On your problem: The page at http://inkscape.modevia.com/doxygen/html/path-prefix_8h-source.php differs from my checked out version.
Are you working from svn or from some tarball?
On Jun 3, 2006, at 2:37 PM, Ben Fowler wrote:
On 03/06/06, Jon A. Cruz <jon@...18...> wrote:
On Jun 3, 2006, at 10:57 AM, David Vincent Himelright wrote:
FYI, I just joined inkscape-devel and I'm building on Mac OS X/ PPC. There are some redefinitions of preprocessor macros in path- prefix.h that break the build on my platform (CREATE_GRADIENTSDIR, CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
Can you point out which OS X version, etc. you have?
This is a True Bill, but I thought that it been fixed in svn.
On Jun 3, 2006, at 4:26 PM, Ben Fowler wrote:
On 03/06/06, David Himelright <himelright.2@...1307...> wrote:
Hmm, that is odd. I've been working from svn, hacked path-prefix.h up a few weeks ago. I'm thinking that the issue was fixed in source control before I even raised the issue. I've nuked the patched version of path-prefix.h and re-checked out from svn (12184), now rebuilding from source, and it looks like the defines are all in place now.
Are you saying that the problem is inactive? You seem to have been doing the same as I, and touch wood, it is O.K. for me.
Yes, unambiguously, yes! My version was bogus. SVN builds for me now, I'm running a fresh compile as I type this.
Re: building universal binaries - I certainly can cross-compile on a PPC system. The step I'd need to take first though would be to completely isolate my build system - including dependencies. I'm currently building support libraries with fink-unstable and while that takes a lot of the work out of patching and configuring dependencies, it also leaves a bit of a mess. I'll see what I can do today about cleaning up, isolating and rebuilding dependencies (gtk, gtkmm, pango) from source outside of the system path.
There was something on the list about two weeks ago, and whilst I haven't built on Tiger since then, I beleive that the ;standard methods' are working.
I'll look at the build doc and try to get things scripted out using the canonical process, now that I've run the gauntlet a couple of times with training wheels (using the package manager).
Thanks Ben,
--David
Ben.
On Jun 3, 2006, at 3:12 PM, Ben Fowler wrote:
On 03/06/06, David Himelright <himelright.2@...1307...> wrote:
I'm building at home on a Tiger (10.4.6) G4 system, and we've got some G5s at work running other versions.
Incidentally, I wish our lab had some Intel Macs so I could offer to patch the packaging scripts for universal binary, but I might be able to find one if I look around.
David, we very definitely need someone to investigate producing a Universal Binary for version 0.44; I cannot see my way to doing anything about it.
You might want to look at http://developer.apple.com/opensource/ buildingopensourceuniversal.html which I came acroos about a week ago whilst looking for something else.
On your problem: The page at http://inkscape.modevia.com/doxygen/html/path-prefix_8h-source.php differs from my checked out version.
Are you working from svn or from some tarball?
On Jun 3, 2006, at 2:37 PM, Ben Fowler wrote:
On 03/06/06, Jon A. Cruz <jon@...18...> wrote:
On Jun 3, 2006, at 10:57 AM, David Vincent Himelright wrote:
> FYI, I just joined inkscape-devel and I'm building on Mac OS X/ > PPC. > There are some redefinitions of preprocessor macros in path- > prefix.h > that break the build on my platform (CREATE_GRADIENTSDIR, > CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
Can you point out which OS X version, etc. you have?
This is a True Bill, but I thought that it been fixed in svn.
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Sat, 3 Jun 2006, Ben Fowler wrote:
On 03/06/06, David Himelright <himelright.2@...1307...> wrote:
I'm building at home on a Tiger (10.4.6) G4 system, and we've got some G5s at work running other versions.
Incidentally, I wish our lab had some Intel Macs so I could offer to patch the packaging scripts for universal binary, but I might be able to find one if I look around.
David, we very definitely need someone to investigate producing a Universal Binary for version 0.44; I cannot see my way to doing anything about it.
There is a request in the tracker for Universal binaries, please add a comment if you have time. I marked it very low priority since despite being something we'd all like in theory, it is highly dependant on the availability of hardware and developers and we'd be very lucky for it to happen at all.
Dont suppose Apple provide a free cross compiler? I'm well pleased by the cross compiled Inkscape binaries for windows.
I'm building at home on a Tiger (10.4.6) G4 system, and we've got some G5s at work running other versions.
Incidentally, I wish our lab had some Intel Macs so I could offer to patch the packaging scripts for universal binary, but I might be able to find one if I look around.
David, we very definitely need someone to investigate producing a Universal Binary for version 0.44; I cannot see my way to doing anything about it.
There is a request in the tracker for Universal binaries, please add a comment if you have time. I marked it very low priority since despite being something we'd all like in theory, it is highly dependant on the availability of hardware and developers and we'd be very lucky for it to happen at all.
What would building the Universal binary entail? Would the machine be needed just for the build, or would it be needed for extended testing?
I have several friends with x86 Macs. If I didn't need to have their computers for very long, I may be able to get my hands on one. I doubt they'd be willing to live without their loved ones for more than a week.
Would I just need to follow the same instructions as on this page? http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX I've never packaged before, though I'm familiar with fink on PPC (my wife has a Mac).
I guess what I'm saying is that I can probably get access to the hardware if someone is willing to do a bit of hand-holding.
Thanks,
On Sat, 3 Jun 2006, Michael Moore wrote:
David, we very definitely need someone to investigate producing a Universal Binary for version 0.44; I cannot see my way to doing anything about it.
There is a request in the tracker for Universal binaries, please add a comment if you have time. I marked it very low priority since despite being something we'd all like in theory, it is highly dependant on the availability of hardware and developers and we'd be very lucky for it to happen at all.
What would building the Universal binary entail? Would the machine be needed just for the build, or would it be needed for extended testing?
Would I just need to follow the same instructions as on this page? http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX I've never packaged before, though I'm familiar with fink on PPC (my wife has a Mac).
I guess what I'm saying is that I can probably get access to the hardware if someone is willing to do a bit of hand-holding.
See the mail I was writing as you posted this, since it answers a few questions. In theory, the machine would mostly just be needed for the builds, but at the beginning I imagine a fair amout of testing too. Especially as bug reports come in for the Intel version.
Unfortunately there are no documented instructions for building a Universal version of Mac because none of us have ever done it. (They would obviously be documented once we had the procedure worked out.)
For creating a Universal binary I suspect we need better access to a machine than what you could offer though friends computers, but thankyou anyway.
Having said this, you could just follow the instuctions on the CompilingMacOsX wiki page to just build a version for Intel using any Intel based Mac -- it's exactly the same process as for a PPC Mac, though your friends would need to give you admin rights to install the relevant fink dependencies (or do it themselves).
Cheers, Michael
On Jun 3, 2006, at 8:32 PM, Michael Moore wrote:
What would building the Universal binary entail? Would the machine be needed just for the build, or would it be needed for extended testing?
Would I just need to follow the same instructions as on this page? http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX I've never packaged before, though I'm familiar with fink on PPC (my wife has a Mac).
I guess what I'm saying is that I can probably get access to the hardware if someone is willing to do a bit of hand-holding.
Hi Michael,
a couple of things right off the bat. The launcher application that runs X11 will need to be recompiled as universal. It may actually work in emulation under Rosetta, but it may not, and it'll certainly be slow. It's the app in 'src/packaging/ScriptExec'.
To compile universal binaries, you'll want the most recent version of Apple's developer tools (XCode 2.3), which updates Apple's gcc and libtool and comes with lipo. Beyond that, I'm willing to help out and field questions about the Mac side of things. I'm pretty much a GTK and Inkscape noob, but I've been porting apps to the Mac from Windows for years.
--David
On Sat, 3 Jun 2006, David Himelright wrote:
a couple of things right off the bat. The launcher application that runs X11 will need to be recompiled as universal. It may actually work in emulation under Rosetta, but it may not, and it'll certainly be slow.
Quite true. This can actually be done now. The launcher itself has no dendencies and is a standard Xcode project. So should eb able to be built as Universal on any Mac.
It's the app in 'src/packaging/ScriptExec'.
I know, I put it there. ;-)
To compile universal binaries, you'll want the most recent version of Apple's developer tools (XCode 2.3), which updates Apple's gcc and libtool and comes with lipo.
Yep, been using that to build the 0.44 prereleases.
Beyond that, I'm willing to help out and field questions about the Mac side of things. I'm pretty much a GTK and Inkscape noob, but I've been porting apps to the Mac from Windows for years.
Thankyou. Much appreciated!
Cheers, Michael
On Jun 3, 2006, at 9:41 PM, Michael Wybrow wrote:
On Sat, 3 Jun 2006, David Himelright wrote:
a couple of things right off the bat. The launcher application that runs X11 will need to be recompiled as universal. It may actually work in emulation under Rosetta, but it may not, and it'll certainly be slow.
Quite true. This can actually be done now. The launcher itself has no dendencies and is a standard Xcode project. So should eb able to be built as Universal on any Mac.
It's the app in 'src/packaging/ScriptExec'.
I know, I put it there. ;-)
To compile universal binaries, you'll want the most recent version of Apple's developer tools (XCode 2.3), which updates Apple's gcc and libtool and comes with lipo.
Yep, been using that to build the 0.44 prereleases.
Beyond that, I'm willing to help out and field questions about the Mac side of things. I'm pretty much a GTK and Inkscape noob, but I've been porting apps to the Mac from Windows for years.
Thankyou. Much appreciated!
Cheers, Michael
Well, I was addressing the other Micheal, but now I know who the Mac maven is ;-) Good to know! I really like this project, and I'm looking forward to the immendio GTK+ Mac port sometime down the road.
--David
On Sat, 3 Jun 2006, David Himelright wrote:
Well, I was addressing the other Micheal, but now I know who the Mac maven is ;-) Good to know!
*sigh* I realised this upon reading back the thread in the correct order. Sorry about that.
... I'm looking forward to the immendio GTK+ Mac port sometime down the road.
Yes, that is going to be very exciting.
Cheers, Michael Wybrow
On Sun, 4 Jun 2006, Alan Horkan wrote:
On Sat, 3 Jun 2006, Ben Fowler wrote:
On 03/06/06, David Himelright <himelright.2@...1307...> wrote:
Incidentally, I wish our lab had some Intel Macs so I could offer to patch the packaging scripts for universal binary, but I might be able to find one if I look around.
David, we very definitely need someone to investigate producing a Universal Binary for version 0.44; I cannot see my way to doing anything about it.
There is a request in the tracker for Universal binaries, please add a comment if you have time. I marked it very low priority since despite being something we'd all like in theory, it is highly dependant on the availability of hardware and developers and we'd be very lucky for it to happen at all.
In theory I know how to do it. I've done some reading as well as quizing Aaron Voisine on the process he uses to build a Universal version of Gimp.app. The easiest way to do this is to build two idential versions on two machines (one PPC, one x86) and use the Apple tool lipo to build a single universal version of each of the executables/libraries from the different arcitecture versions. This is what is done for Gimp.app.
(lipo man page: http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/lipo...)
The only reason I have not yet tried the above approach is that I don't have access to an Intel MAC. I was actually thinking that one good use of Inkscape's savings might be to purchase a cheap Intel Mac (i.e, MacMini). In theory one would only need shell access so this headless box could live anywhere as long as it had a fast connection. Probably though it would be better if it lived with one of the Mac developers so some amount of testing could be done.
I'd been thinking in the last few days that it might be ok for such a machine to live at Monash University, since there are now four or five from our research group contributing to Inkscape. I haven't yet talked to our supervisor or any of the tech people but that was an idea. I do think it is really important to have an Intel build of Inkscape for 0.44 or shortly after.
In theory you could try rebuilding a fink tree with all Inkscape's dependencies compiled as Universal libraries, though I imagine this would be more trouble that it is worth.
Dont suppose Apple provide a free cross compiler? I'm well pleased by the cross compiled Inkscape binaries for windows.
Yes, Apple's gcc-4.0 is a cross compiler. It can build target code for either PPC or x86. The problem is that building or app bundle requires having Universal (dual arcitecture) copies of all the fink libraries that we drag into the app bundle.
Cheers, Michael
On Sat, 3 Jun 2006, Ben Fowler wrote:
On 03/06/06, Jon A. Cruz <jon@...18...> wrote:
On Jun 3, 2006, at 10:57 AM, David Vincent Himelright wrote:
FYI, I just joined inkscape-devel and I'm building on Mac OS X/PPC. There are some redefinitions of preprocessor macros in path-prefix.h that break the build on my platform (CREATE_GRADIENTSDIR, CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
Can you point out which OS X version, etc. you have?
This is a True Bill, but I thought that it been fixed in svn.
This was a problem in the 0.44pre0 tarball, but only if you compiled with "--enable-osxapp" to attempt to build an app bundle. It was quickly fixed it SVN and the fix is present in the 0.44pre1 tarball.
Cheers, Michael
The CREATE Directories are outside of Inkscape dir due to the fact that this is support for the CREATE project and the directories are not determine by Inkscape directly. If you having a patch please add it to the patch track and notify the ML.
thank you, Joshua L. Blocher verbalshadow On 6/3/06, David Vincent Himelright <himelright.2@...1307...> wrote:
FYI, I just joined inkscape-devel and I'm building on Mac OS X/PPC. There are some redefinitions of preprocessor macros in path-prefix.h that break the build on my platform (CREATE_GRADIENTSDIR, CREATE_PALETTESDIR, CREATE_PATTERNSDIR).
It's pretty clear that most of the paths that now point to locations inside of the application package should probably instead point to the "Application Support" directory in an individual user's home folder for application-generated data. It's less clear to me whether it's a good idea to move a number of the other resource directories outside of the app package simply to be more "mac like" (probably more trouble than it's worth).
I'm planning to spend part of the weekend working on a little extension for some linguistics features (syntax trees), but with builds apparently slightly broken on OS X (one minor change necessary), I'd be more than happy to contribute a patch, work with the Mac module owner, and test.
David Himelright
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (8)
-
Alan Horkan -
Ben Fowler -
David Himelright -
David Vincent Himelright -
Jon A. Cruz -
Joshua Blocher -
Michael Moore -
Michael Wybrow