os x packaging problems (in CVS)
hi list,
I experienced some packaging problems since I use --enable-osxapp and since the reopening of HEAD (I don't know which of these could cause the problem). I hoped that Michael commits will solve them but here is what I see:
1/. I package with the instruction: ./osx-app.sh ../../inkscape_compiled/bin/inkscape ../Info.plist macosx everything seems to run fine but when I double click the newly created app I receive an error message: "You cannot open the application "Inkscape" because it may be damaged or incomplete." I looked into the app bundle and it lacks the executable so obviously it cannot run. If I run the executable from the command line in my prefix dir it works (but does not find many stuff because I compiled with the --enable-osxapp configuration option).
2/. Then I copied the executable to the app bundle. The message is gone and the application only briefly appears in the dock before quitting and in my console log I have the message:
** (process:10080): WARNING **: Could not open units file 'Contents/ Resources/ui/units.txt': No such file or directory
** (process:10080): WARNING **: * INKSCAPE_DATADIR is: '/Volumes/ files/softwares/inkscape_compiled//share'
** (process:10080): WARNING **: * INKSCAPE_UIDIR is: 'Contents/ Resources/ui'
Nothing to do!
Though, the ui directory is present in the .app bundle and readable as well as everything inside it. Maybe it looks for it in "/Volumes/ files/softwares/inkscape_compiled//share" which is my prefix dir. It should look where the bundle is... I'm using Xcode 2.1 on 10.4 and I remarked that when packaging gcc-4.0 is used by default while I compiled inkscape with gcc 3.3. could it matter? then, how could I change Xcode's default? Also I compile with an additional option as an environment variable as Michael advised: export ac_cv_lib_intl_dgettext="yes"
Any help will be appreciated. With the numerous commits into cvs I would like to build some new development builds so that people could test the new features.
JiHO --- Windows, c'est un peu comme le beaujolais nouveau : a chaque nouvelle cuvee on sait que ce sera degueulasse, mais on en prend quand meme par masochisme. --- http://jo.irisson.free.fr/
On Sun, 20 Nov 2005, jiho wrote:
I experienced some packaging problems since I use --enable-osxapp and since the reopening of HEAD (I don't know which of these could cause the problem). I hoped that Michael commits will solve them but here is what I see:
[...]
Any help will be appreciated. With the numerous commits into cvs I would like to build some new development builds so that people could test the new features.
The problem was a typo in one of my recent changes to the packaging script. I was able to reproduce what you were seeing and the fix is now in CVS. Should work again. Sorry about that.
Cheers, Michael
On Mon, 2005-11-21 at 15:37 +1100, Michael Wybrow wrote:
On Sun, 20 Nov 2005, jiho wrote:
I experienced some packaging problems since I use --enable-osxapp and since the reopening of HEAD (I don't know which of these could cause the problem). I hoped that Michael commits will solve them but here is what I see:
[...]
Any help will be appreciated. With the numerous commits into cvs I would like to build some new development builds so that people could test the new features.
The problem was a typo in one of my recent changes to the packaging script. I was able to reproduce what you were seeing and the fix is now in CVS. Should work again. Sorry about that.
Is this enough of a fix so that we can get the mac package out tonite? Or, do we need to wait for a point release?
I'm releasing the formal press release here in a couple of hours, so it would be great to get this all pulled together and posted up on the file tracker prior to mega-publicity.
Jon
On Sun, 20 Nov 2005, Jon Phillips wrote:
On Mon, 2005-11-21 at 15:37 +1100, Michael Wybrow wrote:
The problem was a typo in one of my recent changes to the packaging script. I was able to reproduce what you were seeing and the fix is now in CVS. Should work again. Sorry about that.
Is this enough of a fix so that we can get the mac package out tonite? Or, do we need to wait for a point release?
No, it's been released. I uploaded the dmg for 0.43 and transferred it to the file release section a couple of hours ago.
Only reason it wasn't done sooner was that I've been unwell the last couple of days and that typo prevented jiho from being able to do it either.
Cheers, Michael
On 21 nov. 05, at 05:37, Michael Wybrow wrote:
On Sun, 20 Nov 2005, jiho wrote:
I experienced some packaging problems since I use --enable-osxapp and since the reopening of HEAD (I don't know which of these could cause the problem). I hoped that Michael commits will solve them but here is what I see:
[...]
Any help will be appreciated. With the numerous commits into cvs I would like to build some new development builds so that people could test the new features.
The problem was a typo in one of my recent changes to the packaging script. I was able to reproduce what you were seeing and the fix is now in CVS. Should work again. Sorry about that
no problem. I uploaded a dev build on the site with all recent changes. I stripped it down and used --enable-osxapp and export ac_cv_lib_intl_dgettext="yes" so everything should be fine now. could you please test it? BTW, is export ac_cv_lib_intl_dgettext="yes" still needed? what was the problem exactly? Ahh and one last thing: whiteboard isn't enabled in the dev builds. I will do it next time.
Hope you are well now.
JiHO --- Windows, c'est un peu comme le beaujolais nouveau : a chaque nouvelle cuvee on sait que ce sera degueulasse, mais on en prend quand meme par masochisme. --- http://jo.irisson.free.fr/
On Mon, 21 Nov 2005, jiho wrote:
no problem. I uploaded a dev build on the site with all recent changes. I stripped it down and used --enable-osxapp and export ac_cv_lib_intl_dgettext="yes" so everything should be fine now. could you please test it?
I am unable to test that particular build. I downloaded the Inkscape_20051120.dmg file twice, and both times it said it was unmountable.
BTW, is export ac_cv_lib_intl_dgettext="yes" still needed? what was the problem exactly?
Yes, the problem is a compiler regression in Apple's gcc which causes a configure test for the dgettext function from libintl to fail even when the function is avaible. I haven't yet checked if this is still a problem with the builds of gcc in XCode 2.2. It's needed if using Xcode 2.0 or 2.1.
Cheers, Michael
On 23 nov. 05, at 00:21, Michael Wybrow wrote:
On Mon, 21 Nov 2005, jiho wrote:
no problem. I uploaded a dev build on the site with all recent changes. I stripped it down and used --enable-osxapp and export ac_cv_lib_intl_dgettext="yes" so everything should be fine now. could you please test it?
I am unable to test that particular build. I downloaded the Inkscape_20051120.dmg file twice, and both times it said it was unmountable.
my local file mounts fine but I have the same problem with the one downloaded. it must be an upload problem (cyberduck said it was fine though...). I re-uploaded it right now and tested. it works fine. I'll use scp know and forget about all these crappy GUI applications ;-)
JiHO --- Windows, c'est un peu comme le beaujolais nouveau : a chaque nouvelle cuvee on sait que ce sera degueulasse, mais on en prend quand meme par masochisme. --- http://jo.irisson.free.fr/
participants (3)
-
jiho -
Jon Phillips -
Michael Wybrow