Re: [Inkscape-devel] Intel Aqua packaging
On 8/4/10 13:40, Lloyd Sargent wrote:
Okay, I went back and looked at the build info and I've found two problems:
#1.
<...>
The following build commands failed: ScriptExec: ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-fufpslfnljyhqverjsxrfdvyqeus/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal ppc c com.apple.compilers.gcc.4_2 ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-ewyzzpalxmpnnsapxxvoyqkdnuir/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal i386 c com.apple.compilers.gcc.4_2 (2 failures)
See my earlier answer to Stuart:
On 22/3/10 14:00, ~suv wrote:
Yes, the lack of MacOSX10.4u.sdk is obviously significant for the available xcodeproject of the application launcher. Please be aware that the release version 0.47 was not built on Snow Leopard, nor are the current development snapshots built on Snow Leopard. I.e. you are trying to do something new that seems to require part of the packaging modules to be modified and updated to run on OS X 10.6 Snow Leopard.
I recommend to file a bug report, detailing the SL related errors you see when trying to package the application. Please include all relevant information about your OS and Xcode version.
I'm not familiar with Xcode projects and don't know what changes are needed to compile 'ScriptExec' on Snow Leopard. Earlier in this thread it was mentioned to use gcc 4.0 instead of gcc 4.2 when employing the MacOSX10.4u.sdk on SL, but I don't know which changes you'd have to make to which files to change the compiler for the Xcode project only (you don't want to downgrade the compiler when building MacPorts or Inkscape itself).
Looking at your error messages I see two issues to be addressed: 1) carbon vs cocoa (i.e. has anyone tried to create a new application launcher - ScriptExec - based on a current version of Platypus that might build with the 10.5 or 10.6 SDK?) 2) Universal build for PPC/i386 as target? (i.e. do we need 'ScriptExec' to be built Universal on Snow Leopard, and if so, does it need to support PPC - considering that SL doesn't run on PPC arch - or should the (platypus) launcher application be built either as Universal i386/x86_64 or as x86_64 only on Snow Leopard?).
#2
cp: /opt/local/etc/pango/pangox.aliases: No such file or directory
Which makes sense as I have no pangox.aliases... what package would this be from. I've built and installed pango, so that's not the problem...
Has been answered in this thread already: the file is installed by pango when compiled with support for the X font backend. AFAICT the file is not needed when using Inkscape with GTK+/Quartz and both the packaging scripts and the application launcher script put inside the application package will have to be adapted to not look for this file when building/launching Inkscape without X11:
On 22/3/10 14:00, ~suv wrote:
The GTK+/Quartz (so-called "Aqua") version will also require changes to both the build scripts and the launcher scripts - but this should be handled in a separate bug report, similar to the one Wolf filed for removing the code launching X11 on Tiger.
~suv
On Apr 8, 2010, at 9:05 AM, ~suv wrote:
On 8/4/10 13:40, Lloyd Sargent wrote:
Okay, I went back and looked at the build info and I've found two problems:
#1.
<...>
The following build commands failed: ScriptExec: ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-fufpslfnljyhqverjsxrfdvyqeus/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal ppc c com.apple.compilers.gcc.4_2 ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-ewyzzpalxmpnnsapxxvoyqkdnuir/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal i386 c com.apple.compilers.gcc.4_2 (2 failures)
See my earlier answer to Stuart:
On 22/3/10 14:00, ~suv wrote:
Yes, the lack of MacOSX10.4u.sdk is obviously significant for the available xcodeproject of the application launcher. Please be aware that the release version 0.47 was not built on Snow Leopard, nor are the current development snapshots built on Snow Leopard. I.e. you are trying to do something new that seems to require part of the packaging modules to be modified and updated to run on OS X 10.6 Snow Leopard.
I recommend to file a bug report, detailing the SL related errors you see when trying to package the application. Please include all relevant information about your OS and Xcode version.
I'm not familiar with Xcode projects and don't know what changes are needed to compile 'ScriptExec' on Snow Leopard. Earlier in this thread it was mentioned to use gcc 4.0 instead of gcc 4.2 when employing the MacOSX10.4u.sdk on SL, but I don't know which changes you'd have to make to which files to change the compiler for the Xcode project only (you don't want to downgrade the compiler when building MacPorts or Inkscape itself).
Looking at your error messages I see two issues to be addressed:
- carbon vs cocoa (i.e. has anyone tried to create a new application
launcher - ScriptExec - based on a current version of Platypus that might build with the 10.5 or 10.6 SDK?) 2) Universal build for PPC/i386 as target? (i.e. do we need 'ScriptExec' to be built Universal on Snow Leopard, and if so, does it need to support PPC - considering that SL doesn't run on PPC arch - or should the (platypus) launcher application be built either as Universal i386/x86_64 or as x86_64 only on Snow Leopard?).
I would be willing to give it a go. I really would like Inkscape running on my MacPro (as would many other people).
#2
cp: /opt/local/etc/pango/pangox.aliases: No such file or directory
Which makes sense as I have no pangox.aliases... what package would this be from. I've built and installed pango, so that's not the problem...
Has been answered in this thread already: the file is installed by pango when compiled with support for the X font backend. AFAICT the file is not needed when using Inkscape with GTK+/Quartz and both the packaging scripts and the application launcher script put inside the application package will have to be adapted to not look for this file when building/launching Inkscape without X11:
I'll go hunt it down...
The directions I followed were from here "http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX"
On 22/3/10 14:00, ~suv wrote:
The GTK+/Quartz (so-called "Aqua") version will also require changes to both the build scripts and the launcher scripts - but this should be handled in a separate bug report, similar to the one Wolf filed for removing the code launching X11 on Tiger.
~suv
On Apr 8, 2010, at 11:54 AM, Lloyd Sargent wrote:
On Apr 8, 2010, at 9:05 AM, ~suv wrote:
On 8/4/10 13:40, Lloyd Sargent wrote:
Okay, I went back and looked at the build info and I've found two problems:
#1.
<...>
The following build commands failed: ScriptExec: ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-fufpslfnljyhqverjsxrfdvyqeus/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal ppc c com.apple.compilers.gcc.4_2 ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-ewyzzpalxmpnnsapxxvoyqkdnuir/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal i386 c com.apple.compilers.gcc.4_2 (2 failures)
See my earlier answer to Stuart:
On 22/3/10 14:00, ~suv wrote:
Yes, the lack of MacOSX10.4u.sdk is obviously significant for the available xcodeproject of the application launcher. Please be aware that the release version 0.47 was not built on Snow Leopard, nor are the current development snapshots built on Snow Leopard. I.e. you are trying to do something new that seems to require part of the packaging modules to be modified and updated to run on OS X 10.6 Snow Leopard.
I recommend to file a bug report, detailing the SL related errors you see when trying to package the application. Please include all relevant information about your OS and Xcode version.
I'm not familiar with Xcode projects and don't know what changes are needed to compile 'ScriptExec' on Snow Leopard. Earlier in this thread it was mentioned to use gcc 4.0 instead of gcc 4.2 when employing the MacOSX10.4u.sdk on SL, but I don't know which changes you'd have to make to which files to change the compiler for the Xcode project only (you don't want to downgrade the compiler when building MacPorts or Inkscape itself).
Looking at your error messages I see two issues to be addressed:
- carbon vs cocoa (i.e. has anyone tried to create a new application
launcher - ScriptExec - based on a current version of Platypus that might build with the 10.5 or 10.6 SDK?) 2) Universal build for PPC/i386 as target? (i.e. do we need 'ScriptExec' to be built Universal on Snow Leopard, and if so, does it need to support PPC - considering that SL doesn't run on PPC arch - or should the (platypus) launcher application be built either as Universal i386/x86_64 or as x86_64 only on Snow Leopard?).
I would be willing to give it a go. I really would like Inkscape running on my MacPro (as would many other people).
#2
cp: /opt/local/etc/pango/pangox.aliases: No such file or directory
Which makes sense as I have no pangox.aliases... what package would this be from. I've built and installed pango, so that's not the problem...
Has been answered in this thread already: the file is installed by pango when compiled with support for the X font backend. AFAICT the file is not needed when using Inkscape with GTK+/Quartz and both the packaging scripts and the application launcher script put inside the application package will have to be adapted to not look for this file when building/launching Inkscape without X11:
I'll go hunt it down...
The directions I followed were from here "http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX"
On 22/3/10 14:00, ~suv wrote:
The GTK+/Quartz (so-called "Aqua") version will also require changes to both the build scripts and the launcher scripts - but this should be handled in a separate bug report, similar to the one Wolf filed for removing the code launching X11 on Tiger.
~suv
Lloyd
Had to take a break from this for a while -- but nice to see someone else entering the battle. However..... be aware that packaging is only part of the problem. In fact, I managed to hack my way past that and have an native app that opens just fine in 10.6.2. But, if you check the related threads (mostly February and March) you'll see that we hit a wall with two big non-packaging issues: first, file open and save causes crashes - always. Second, the second order menu items (actually menus that have second order functions) are just plain missing - so if you want to clip an object for example, you're out of luck. These are the (IMO) primary issues that have to be attended to in order to have some confidence that a properly packaged app will even work. Unfortunately there haven't been any new insights so it's dropped off my to-do list for now. If after reading these threads you have any ideas -- that would be great.
Stu
On Apr 8, 2010, at 3:52 PM, Stuart Edwards wrote:
On Apr 8, 2010, at 11:54 AM, Lloyd Sargent wrote:
On Apr 8, 2010, at 9:05 AM, ~suv wrote:
On 8/4/10 13:40, Lloyd Sargent wrote:
Okay, I went back and looked at the build info and I've found two problems:
#1.
<...>
The following build commands failed: ScriptExec: ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-fufpslfnljyhqverjsxrfdvyqeus/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal ppc c com.apple.compilers.gcc.4_2 ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-ewyzzpalxmpnnsapxxvoyqkdnuir/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal i386 c com.apple.compilers.gcc.4_2 (2 failures)
See my earlier answer to Stuart:
On 22/3/10 14:00, ~suv wrote:
Yes, the lack of MacOSX10.4u.sdk is obviously significant for the available xcodeproject of the application launcher. Please be aware that the release version 0.47 was not built on Snow Leopard, nor are the current development snapshots built on Snow Leopard. I.e. you are trying to do something new that seems to require part of the packaging modules to be modified and updated to run on OS X 10.6 Snow Leopard.
I recommend to file a bug report, detailing the SL related errors you see when trying to package the application. Please include all relevant information about your OS and Xcode version.
I'm not familiar with Xcode projects and don't know what changes are needed to compile 'ScriptExec' on Snow Leopard. Earlier in this thread it was mentioned to use gcc 4.0 instead of gcc 4.2 when employing the MacOSX10.4u.sdk on SL, but I don't know which changes you'd have to make to which files to change the compiler for the Xcode project only (you don't want to downgrade the compiler when building MacPorts or Inkscape itself).
Looking at your error messages I see two issues to be addressed:
- carbon vs cocoa (i.e. has anyone tried to create a new application
launcher - ScriptExec - based on a current version of Platypus that might build with the 10.5 or 10.6 SDK?) 2) Universal build for PPC/i386 as target? (i.e. do we need 'ScriptExec' to be built Universal on Snow Leopard, and if so, does it need to support PPC - considering that SL doesn't run on PPC arch - or should the (platypus) launcher application be built either as Universal i386/x86_64 or as x86_64 only on Snow Leopard?).
I would be willing to give it a go. I really would like Inkscape running on my MacPro (as would many other people).
#2
cp: /opt/local/etc/pango/pangox.aliases: No such file or directory
Which makes sense as I have no pangox.aliases... what package would this be from. I've built and installed pango, so that's not the problem...
Has been answered in this thread already: the file is installed by pango when compiled with support for the X font backend. AFAICT the file is not needed when using Inkscape with GTK+/Quartz and both the packaging scripts and the application launcher script put inside the application package will have to be adapted to not look for this file when building/launching Inkscape without X11:
I'll go hunt it down...
The directions I followed were from here "http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX"
On 22/3/10 14:00, ~suv wrote:
The GTK+/Quartz (so-called "Aqua") version will also require changes to both the build scripts and the launcher scripts - but this should be handled in a separate bug report, similar to the one Wolf filed for removing the code launching X11 on Tiger.
~suv
Lloyd
Had to take a break from this for a while -- but nice to see someone else entering the battle. However..... be aware that packaging is only part of the problem. In fact, I managed to hack my way past that and have an native app that opens just fine in 10.6.2. But, if you check the related threads (mostly February and March) you'll see that we hit a wall with two big non-packaging issues: first, file open and save causes crashes - always. Second, the second order menu items (actually menus that have second order functions) are just plain missing - so if you want to clip an object for example, you're out of luck. These are the (IMO) primary issues that have to be attended to in order to have some confidence that a properly packaged app will even work. Unfortunately there haven't been any new insights so it's dropped off my to-do list for now. If after reading these threads you have any ideas -- that would be great.
As much as I would like too, I suffer from too little time as it is - and this would take me away from several of my current projects (I've been down this road before and it is never pretty). For now I will just run it on Linux under VMWare.
Good luck!
Lloyd
On Apr 8, 2010, at 8:56 PM, Lloyd Sargent wrote:
On Apr 8, 2010, at 3:52 PM, Stuart Edwards wrote:
On Apr 8, 2010, at 11:54 AM, Lloyd Sargent wrote:
On Apr 8, 2010, at 9:05 AM, ~suv wrote:
On 8/4/10 13:40, Lloyd Sargent wrote:
Okay, I went back and looked at the build info and I've found two problems:
#1.
<...>
The following build commands failed: ScriptExec: ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-fufpslfnljyhqverjsxrfdvyqeus/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal ppc c com.apple.compilers.gcc.4_2 ProcessPCH /var/folders/D+/D+KS42xe2RWRN++1YwAjD++++TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/ScriptExec_Prefix-ewyzzpalxmpnnsapxxvoyqkdnuir/ScriptExec_Prefix.pch.gch ScriptExec_Prefix.pch normal i386 c com.apple.compilers.gcc.4_2 (2 failures)
See my earlier answer to Stuart:
On 22/3/10 14:00, ~suv wrote:
Yes, the lack of MacOSX10.4u.sdk is obviously significant for the available xcodeproject of the application launcher. Please be aware that the release version 0.47 was not built on Snow Leopard, nor are the current development snapshots built on Snow Leopard. I.e. you are trying to do something new that seems to require part of the packaging modules to be modified and updated to run on OS X 10.6 Snow Leopard.
I recommend to file a bug report, detailing the SL related errors you see when trying to package the application. Please include all relevant information about your OS and Xcode version.
I'm not familiar with Xcode projects and don't know what changes are needed to compile 'ScriptExec' on Snow Leopard. Earlier in this thread it was mentioned to use gcc 4.0 instead of gcc 4.2 when employing the MacOSX10.4u.sdk on SL, but I don't know which changes you'd have to make to which files to change the compiler for the Xcode project only (you don't want to downgrade the compiler when building MacPorts or Inkscape itself).
Looking at your error messages I see two issues to be addressed:
- carbon vs cocoa (i.e. has anyone tried to create a new application
launcher - ScriptExec - based on a current version of Platypus that might build with the 10.5 or 10.6 SDK?) 2) Universal build for PPC/i386 as target? (i.e. do we need 'ScriptExec' to be built Universal on Snow Leopard, and if so, does it need to support PPC - considering that SL doesn't run on PPC arch - or should the (platypus) launcher application be built either as Universal i386/x86_64 or as x86_64 only on Snow Leopard?).
I would be willing to give it a go. I really would like Inkscape running on my MacPro (as would many other people).
#2
cp: /opt/local/etc/pango/pangox.aliases: No such file or directory
Which makes sense as I have no pangox.aliases... what package would this be from. I've built and installed pango, so that's not the problem...
Has been answered in this thread already: the file is installed by pango when compiled with support for the X font backend. AFAICT the file is not needed when using Inkscape with GTK+/Quartz and both the packaging scripts and the application launcher script put inside the application package will have to be adapted to not look for this file when building/launching Inkscape without X11:
I'll go hunt it down...
The directions I followed were from here "http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX"
On 22/3/10 14:00, ~suv wrote:
The GTK+/Quartz (so-called "Aqua") version will also require changes to both the build scripts and the launcher scripts - but this should be handled in a separate bug report, similar to the one Wolf filed for removing the code launching X11 on Tiger.
~suv
Lloyd
Had to take a break from this for a while -- but nice to see someone else entering the battle. However..... be aware that packaging is only part of the problem. In fact, I managed to hack my way past that and have an native app that opens just fine in 10.6.2. But, if you check the related threads (mostly February and March) you'll see that we hit a wall with two big non-packaging issues: first, file open and save causes crashes - always. Second, the second order menu items (actually menus that have second order functions) are just plain missing - so if you want to clip an object for example, you're out of luck. These are the (IMO) primary issues that have to be attended to in order to have some confidence that a properly packaged app will even work. Unfortunately there haven't been any new insights so it's dropped off my to-do list for now. If after reading these threads you have any ideas -- that would be great.
As much as I would like too, I suffer from too little time as it is - and this would take me away from several of my current projects (I've been down this road before and it is never pretty). For now I will just run it on Linux under VMWare.
Good luck!
Lloyd
I assume you know that it runs fine on Snow Leopard under X11
Stu
participants (3)
-
Lloyd Sargent -
Stuart Edwards -
~suv