Several questions regarding compiling BaCon
Jan 6, 2015 23:07:06 GMT 1
Post by dave99 on Jan 6, 2015 23:07:06 GMT 1
Hi all
Up to now I have been using bacon.bash to compile my .bac pgms but it wastes a lot of time so I would like to compile bacon.bac
==============
Question 1
==============
Do I compile bacon.bac as follows ?
bacon.bash bacon.bac
(I'm not too concerned about stripping the resulting executable).
=============
Question 2
=============
How do I compile hug.bac so that it's a .so and not a "normal" elf executable ?
=============
Question 3
=============
Once bacon.bac and hug.bac are compiled, where do I put them?
=============
Question 4
=============
Currently when I compile a bacon pgm, there are no unusual dependencies and I often compile on Puppy Linux and then use
the resulting executable on other distros with no problems , but if I compile
bacon and use hug, I assume that I have to also distribute hug.so if I distribute a compiled bacon pgm
or does it use static linking from hug.so?
=============
Question 5
=============
When using the compiled bacon (instead of bacon.bash), I would need to change INCLUDE "hug.bac"
to INCLUDE "hug_imports.bac" but where do I get the latest hug_imports.bac?
From here www.basic-converter.org/hug_imports.bac ?
=============
Question 6
=============
When I write a new BaCon pgm, I use separate directories for each pgm, like so:
/root/Bacon/pgms/MyPgm1
and
/root/Bacon/pgms/MyPgm2
and so on.
I then compile as follows, bacon.bash /root/Bacon/pgms/MyPgm2/MyPgm2.bac
The reason I do this two fold, firstly to keep my sources organized and secondly if there is an error, it's easy to clean up
all the .h files left behind.
I assume that compiling with the compiled version of BaCon is the same and it would generate all the .h files in the same directory
as the source .bac file ?
Thanks in advance.
Dave.
Up to now I have been using bacon.bash to compile my .bac pgms but it wastes a lot of time so I would like to compile bacon.bac
==============
Question 1
==============
Do I compile bacon.bac as follows ?
bacon.bash bacon.bac
(I'm not too concerned about stripping the resulting executable).
=============
Question 2
=============
How do I compile hug.bac so that it's a .so and not a "normal" elf executable ?
=============
Question 3
=============
Once bacon.bac and hug.bac are compiled, where do I put them?
=============
Question 4
=============
Currently when I compile a bacon pgm, there are no unusual dependencies and I often compile on Puppy Linux and then use
the resulting executable on other distros with no problems , but if I compile
bacon and use hug, I assume that I have to also distribute hug.so if I distribute a compiled bacon pgm
or does it use static linking from hug.so?
=============
Question 5
=============
When using the compiled bacon (instead of bacon.bash), I would need to change INCLUDE "hug.bac"
to INCLUDE "hug_imports.bac" but where do I get the latest hug_imports.bac?
From here www.basic-converter.org/hug_imports.bac ?
=============
Question 6
=============
When I write a new BaCon pgm, I use separate directories for each pgm, like so:
/root/Bacon/pgms/MyPgm1
and
/root/Bacon/pgms/MyPgm2
and so on.
I then compile as follows, bacon.bash /root/Bacon/pgms/MyPgm2/MyPgm2.bac
The reason I do this two fold, firstly to keep my sources organized and secondly if there is an error, it's easy to clean up
all the .h files left behind.
I assume that compiling with the compiled version of BaCon is the same and it would generate all the .h files in the same directory
as the source .bac file ?
Thanks in advance.
Dave.