Q_Liberator malaise

[RalfR]

That was a very good idea!

[pjw]

Thanks Martin!
Id be more interested in a utility to entirely remove any built in runtimes..

[dilwyn]

Thanks Martin!
Id be more interested in a utility to entirely remove any built in runtimes..

Me too, although both removal and addition are useful tools.

[Peter]

I don't know if there is any interest in this, But this program will add the runtimes to a compiled program that does not have them.

At the moment I use only QLib programs which already have a built-in in runtime, but it's good to have, just in case.
Many thanks.

[RalfR]

At the moment I use only QLib programs which already have a built-in in runtime

The solution is actually quite simple: simply load "QLib_run" in the boot program, then everything will work....

[tofro]

At the moment I use only QLib programs which already have a built-in in runtime

The solution is actually quite simple: simply load "QLib_run" in the boot program, then everything will work....

A solution is only necessary if you think there is a problem. I have no problems with (rather, I prefer, like Peter) self-contained programs that come with their runtimes. This preference probably depends on how many QLiberated programs you use.

[dilwyn]

Nice to have the option, I suppose.

[pjw]

I normally load up Qlib_run, Turbo_TK, ptrmen, Qmenu, PHGTK, Dbas, and a bunch of other "standard" toolkits and system extensions in my boot file so I dont have to faff around every time I want to fire up some well-worn - or rarely used - program, or to test anything new. I run the same boot file across all the systems I use for anything other than testing.

It doesnt matter whether the runtimes are included or not, the program will work either way. Its just that niggly feeling about the unnecessary bloatware, so it would be good to have the possibility to get rid of it.

Of course if you only run the same three old programs on your "QL", then theres no need to change. You probably then use some kind of PC to do any "real" work.