BBC BASIC for Windows
« Compile embedded file list »
Welcome Guest. Please Login or Register. Apr 5th, 2018, 10:40pm
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
If you require a dump of the post on your message board, please come to the support board and request it.
Topic: Compile embedded file list (Read 706 times)
Malvern Guest
Compile embedded file list
« Thread started on: Feb 25th, 2012, 1:42pm »
The current compile gets Install file names even from remmed lines and strings. It looks as if the Find code is used and thus it can insert garbage names into the list. PROCout(F%,1,"REM INSTALL @lib$+"+CHR$34+"WINLIB2"+CHR$34+" near ..... for instance would show a non-existent file name in the list.
The current compile gets Install file names even from remmed lines and strings.
Yes, it's pretty unsophisticated and only intended to make a guess at the files that require embedding.
The important point here is that this method of discovering which files need to be embedded is a fallback: it only gets used when there is neither an existing executable nor a REM!Embed directive present.
If there are one or more REM!Embed directives in the program then they determine the files that will be embedded in the executable, so this is the best method to use. If there is no REM!Embed but there is an existing executable file (in the default location) then the list of embedded files will be taken from that.
So it really doesn't matter that the 'fallback' method is fairly crude.
Logged
