Re: [Pyobjc-dev] PyObjC sources bundled with pbxbuild install

[Dinu G. <gh...@da...>]

bb...@ma...:

> For PBX builds, you could add a shell script build phase that
> invokes a script-- python, likely-- to walk the built tree and
> remove any cruft (including CVS directories!).

Of course, but it would be cleaner and more consistent to include
only what's needed from the start. So far, I have no idea where
and when it is defined what ends up in the PyObjC folder. Is it
in the PB templates?

Another related thing is that doing a "pbxbuild build" is just not
enough to create the full thing and "pbxbuild install" copies the
final .app into a temporary directory from where I have to move it
out again. I suppose this is a setting in PB, maybe in the targets?
Ok, in fact, if you deselect an install directory there it ends up
in build/UninstalledProducts, which is more predictable, I guess.

Also, it seems that a project.pbxproj file contains an item like
this:

		77AD459403ECA7A6004B557F = {
			includeInIndex = 1;
			isa = PBXFolderReference;
			name = PyObjC;
			path = "/usr/lib/python2.2/site-packages/PyObjC";
			refType = 0;
		};

I'm not sure, if one can provide regular expressions in these items
like with Unix find. Probably one could do something equivalent when
building the template (at the risk of being out of being out of synch
after the next CVS compile, but ok, distutils could update the tem-
plates as well). What do you think?

Ideally, there would be a hook for PB to do something during the in-
stantiation of such a template (like with the Installer.app), but I'm
not sure if there is such a functionality...

Dinu

--
Dinu C. Gherman
......................................................................
"One of the common denominators I found is that expectations rise
above that which is expected."
(George W. Bush, 27 Sep. 2000)