Ah thanks Charles, I'd misunderstood - that's just what I needed.
cheers,
Ben
On 17/08/2016 08:59, Charles Warwick wrote:
Hi Ben,
That's exactly what calling that dispatch command will do, if it is executed
in the IDE before you build the standalone.
If the tsNetLibURL stack is unloaded, tsNet will not be included in any
standalone builds that use libURL unless tsNet is selected specifically as an
inclusion.
Regards,
Charles
On 17/08/2016 5:51 pm, Ben Rubinstein wrote:
Thanks Monte.
Is there a way in the build process to include the libURL stack, but not
include the tsNet external?
Ben
On 17/08/2016 00:54, Monte Goulding wrote:
On 17 Aug 2016, at 7:08 AM, Ben Rubinstein <benr...@cogapp.com> wrote:
Is there any way in dp3 to step back a bit further, and include libURL in
a standalone without including tsNet?
At the moment (and perhaps this will be the long term recommendation rather
than any preferences) for projects that don’t want to use tsNet you can do
the following in your main stack initialisation handler (preOpenStack etc):
if the environment is “development” and there is a stack “tsNetLibURL"
then
dispatch “revUnloadLibrary” to stack “tsNetLibURL”
end if
That will cause tsNet to unload itself as the libURL driver and as a
standalone dependency for libURL.
Cheers
Monte
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
