harrow@dec-exodus.UUCP (05/12/86)
Brian recently responded with some suggestions on how to work with the resources of his ETIcon application (THANKS!, Brian). I thought I'd comment on the "fix" that I ended up using: Since I know that the resources WERE in the working standalone application (distributed with the sources), I added the following in the _INIT procedure: OpenResFile ("ETIconed"); This opened the distributed application as just a resource file, and read things from there as needed. Scott (at Reed) also indicated that the Linker does NOT re-create a new file, but only replaces the code segments. Hence, if you one-time create a standalone application file with your ResEdit resources, just use that filename as the output for the Linker (via the BATCH facility?) and the resources will stay there, but you newly compiled code will be inserted. Jeff
dubois@uwmacc.UUCP (Paul DuBois) (05/14/86)
> Scott (at Reed) also indicated that the Linker does NOT re-create > a new file, but only replaces the code segments. Hence, if you > one-time create a standalone application file with your ResEdit > resources, just use that filename as the output for the Linker > (via the BATCH facility?) and the resources will stay there, but > you newly compiled code will be inserted. The linker doesn't even touch the resource fork. It puts the code in the data fork, which is where the supervisor looks for it. -- | Paul DuBois {allegra,ihnp4,seismo}!uwvax!uwmacc!dubois --+-- | Doth the hawk fly by thy wisdom, and stretch her wings | toward the south? Job 39:26