Author |
Topic: LBBRUN.exe and make Executable (Read 202 times) |
|
Richard Russell
Administrator
member is offline
 
Posts: 1348
|
 |
Re: LBBRUN.exe and make Executable
« Reply #3 on: Jan 6th, 2018, 10:22am » |
|
on Jan 6th, 2018, 02:05am, kigohhere wrote:| It is nearly impossible or extremely diffcult for them to distribute their finished programs to other people. Am I right.? |
|
No. It does not follow that because you cannot create a 'standalone executable' you cannot distribute programs to other users (that would be a pretty serious limitation!).
As this is an LBB support group I can use Liberty BASIC as an analogy. LBB supports generating standalone executables (as does BB4W) but LB 4 doesn't (like BBCSDL, currently). However you can of course still distribute your LB program in the form of a 'bundle' (perhaps as a ZIP file) rather than as a single EXE file.
Indeed the analogy is even closer. The way LB 4 works is that you rename the run-time engine to have the same name as your TKN program, but with an EXE extension. When executed it will automatically look for, and run, the TKN (it's a bit like a Windows side-by-side assembly). BBCSDL works in exactly the same way,
Suppose you have created some amazing video game, as the program MyGame.bbc. If you want to distribute it you make a copy of bbcsdl.exe as MyGame.exe and you distribute the two files as a package - possibly in conjunction with the DLLs they need to run. This isn't quite as convenient as a standalone EXE, but it's what LB users have always had to do and it's a perfectly workable solution, at least until there is something better.
Edit: I should add that BBCSDL will never be able to generate a self-contained .EXE file in quite the way that BB4W and LBB do, because of the dependence on SDL. Even if your BASIC program and the run-time engine are combined in a single EXE it will still need the set of SDL, FreeType and Zlib DLLs, just as a distributed LB 4 program needs the SmallTalk DLLs to run.
Strictly speaking one could probably statically link all these components, but it would result in a grossly bloated EXE and the whole point of DLLs is, after all, that they can be shared.
Richard.
|
|
|
|
kigohhere
New Member
member is offline
Posts: 11
|
|
Re: LBBRUN.exe and make Executable
« Reply #4 on: Jan 20th, 2018, 12:43am » |
|
on Jan 6th, 2018, 10:22am, Richard Russell wrote:Indeed the analogy is even closer. The way LB 4 works is that you rename the run-time engine to have the same name as your TKN program, but with an EXE extension. When executed it will automatically look for, and run, the TKN (it's a bit like a Windows side-by-side assembly). BBCSDL works in exactly the same way,
Suppose you have created some amazing video game, as the program MyGame.bbc. If you want to distribute it you make a copy of bbcsdl.exe as MyGame.exe and you distribute the two files as a package - possibly in conjunction with the DLLs they need to run. This isn't quite as convenient as a standalone EXE, but it's what LB users have always had to do and it's a perfectly workable solution, at least until there is something better.
|
|
Hello.
I understand now. 
Your explanation is very detailed and very good!!!!!
Thank you very much!! 
|
|
 Logged
|
|
|
|
|
