Re: Can't pipe files to compileHelp
Re: Can't pipe files to compileHelp
- Subject: Re: Can't pipe files to compileHelp
- From: Bill Cheeseman <email@hidden>
- Date: Sun, 04 Aug 2002 14:51:12 -0400
on 02-08-04 1:12 PM, Jim Correia at email@hidden wrote:
>
> I put a file named "preprocessing.sh" in my project folder's root
>
> level,
>
> with these contents:
>
>
>
> cd "$SRCROOT/English.lproj"
>
> compileHelp -o Help.plist *Help.rtf *Help.rtfd
>
>
Literally? If so, that is your problem.
>
>
When you write ./preprocesing.sh the shell expects an executable.
>
So you'll have to make your script executable (with the executable
>
bit) and have a valid shebang line at the top. Alternatively, you
>
can also write sh preprocessing.sh.
I believe you're mistaken about this. Apple's example of a shell script
phase (in Jaguar) omits the #!/bin/sh at the top of the script. And it works
just fine. I believe this is because you type /bin/sh into the Shell text
field in the script phase build setting in PB, and this generates the
shebang for you. If you look at the build log, you see that this does output
#!/bin/sh just before PB executes the script itself.
Is "shebang" a technical Unix term?
>
Anyway, following your style, I set up a problem which works.
>
>
http://homepage.mac.com/jimcorreia/compileHelpSample.tar.gz
There's something wrong with your example, but I can't quite figure how to
fix it. Or maybe I can. The whole idea is that Help.plist should be a
generated file, yet your project has it already in place. If you remove it
from your project before building, the project will appear to build OK.
However, it fails at run time with an exception saying, basically, that it
can't find Help.plist. The script did generate Help.plist and put it in the
project file, but it never gets put into the built application bundle.
So I think there has to a copy phase in the project, to move the build
Help.plist file into the built application bundle. Am I right about this?
This aspect of PB is new to me, and I haven't tried it yet.
>
In a "real" project, since Help.plist is a strictly generated file,
>
I'd probably generate it into the builds folder and reference it
>
there so it would land in the source folder and want to be checked
>
into revision control.
I think you're saying the same thing I am, except I don't follow the second
half of what you're saying: "reference it there so it would land in the
source folder and want to be checked into revision control." How exactly
would this be accomplished? I do care about localization, by the way, so
having it in English.lproj is important.
Also, I notice that the build folder ends up with a "DerivedSources"
subsubfolder. Is that where the Help.plist file should be placed? Is this
folder automatically generated so it can just be included in the path in
copy phase settings? I'd better go read the documentation (again).
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
The AppleScript Sourcebook -
http://www.AppleScriptSourcebook.com
Vermont Recipes -
http://www.stepwise.com/Articles/VermontRecipes
Croquet Club of Vermont -
http://members.valley.net/croquetvermont
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.