Hi TJ.
In the properties fields of the App object, I believe you have
specified RPYld-06 as the application name for more than one kind of
build, and then have specified that RB provide output from the build
for more than one target, but using the same name.
If you are building for more than one target, and you have specified
the same name for each different output, RB will append stuff to your
name to make sure that one part of the build does not overwrite
another part.
The simplest solution is to specify slightly different names for each
target.
For instance, if you have a build for a Mac specified as RPYld-06, a
build for Windows could not be just RPYld-06, but RPYld-06.exe
If you must build to the same name for some reason, you can avoid
your problem by building for just one target at a time, and making
sure that each build output is moved somewhere safe before building
the next...
HTH
Russ
On Aug 26, 2006, at 9:48 PM, TJ Hanson, PhD wrote:
RB,
I need to rebuild an app that was originally compiled last January.
The application's name is RPYld-06, but the compiled Mac OS X load
module gets automatically labeled by RB as
RPYld-06-Mac OS(Mach-0 PowerPC)
Changing the load module's name after compiling does not work. The
above name is displayed when the program is executed. This name is
far too long and clumsy. I've tried several combinations of loading
names into the App Mac Settings fields. Nothing seems to work.
What's going on and how can I get a Mac OS X load module named
RPYld-06?
The original compile last January was called RPYld-06. Is there
something going on with Release 3 that I don't know about?
Thanks for the help,
TJH
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
