(CCing this to -devel, because it contains some points needing discussion if we want to have more Fink packages based on Xcode projects)

Martin Costabel wrote:
Matthew Sachs wrote:

On Jul 21, 2005, at 13:50, Martin Costabel wrote:

OTOH, if someone knows how to run xcodebuild in such a way that it works for both XC-2.0 and XC-2.1, they are welcome to fix aquaterm correspondingly.

This does work. If the problem is a shell script not being able to find the files, it should use different environment variables. For instance, instead of:
    build/aquaterm/foo-whatever
it should look for:
    $BUILT_PRODUCTS_DIR/foo-whatever

$BUILT_PRODUCTS_DIR will be "build/target" with the default pre-2.1 setup, and "build/config/target" with the default 2.1 setup of per- configuration build directories.
Thanks, this is exactly what is needed (it's build/config on XC-2.1, not build/config/target, but this is the right thing). I committed a new version to CVS, but I can't test it on XC-2.0, I'll have to leave it to Bill and Jens to find out if this works. It works on XC-2.1 in any case.

My response only showed that I understand very little about the command-line API of xcodebuild. But I am learning: You cannot, of course, use xcode's internal environment variables in a shell script that runs xcodebuild (as opposed to a shell script *run by* xcodebuild) - except as write-only variables transmitted to xcodebuild. So this cannot be fixed in the present setting.

In fact, it is not clear to me what is The Right Way to do the equivalent of

 ./configure --prefix=%p
 make
 make install DESTDIR=%d

using xcodebuild. I suspect that there are many different possibilities, but no standard way, because there is no standard for the creation of the project.pbxproj (or whatever the suffix-of-the-week is right now) file which is the equivalent of Makefile, but not really human-readable and -modifiable.

For similar reasons, Fink's current incarnation of the AppBundles field is not really useful, because it makes too many assumptions about the structure of the xcode build process. It is also not well documented; it does not say, for example, what path it is prepending, %b as for the DocFiles field, or %i as for the Files field, or nothing as for the ConfFiles field (these aren't documented either, BTW). I wasn't able to use AppBundles in any of the packages that I have looked at and that produce *.apps: aquaterm, qt3mac, freefem++, texshop, finkcommander.

In any case, I have now checked a new aquaterm.info into CVS that is supposed to work on Xcode-2.0 and -2.1. It uses "xcode install" to build and install the application, instead of copying everything by hand.

Jeff, I apologize for playing around with your package, but I felt I had at least to try to fix it after I broke it :-)

--
Martin



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to