On Fri, Jun 15, 2012 at 8:17 AM, Jeremy Nicoll - ml sourceforge <[email protected]> wrote: > Mark Miesfeld <[email protected]> wrote: > >> If the ooSQLite package gets included in the ooRexx distribution then an >> application written that uses ooSQLite will run on any system where the >> user of the application has ooRexx installed. And the user will not have >> to install anything else. > > But hopefully there's some way that the user can choose to install something > else - a different build of whatever binary you provide, that has a > different SQLite build inside(*) it?
Well sure. All the ooSQLite package consists of is: 06/15/2012 07:33 AM 39,650 ooSQLite.cls 06/15/2012 09:05 AM 779,264 oosqlite.dll If the user wanted to use a different version of ooSQLite then they could replace those files with the version they wanted. Or they could put the different version files some place in the path ahead of those. Or use any other mechanism people use in this type of scenario. On SourceForge we are keeping prior release builds. So some time in the future there might be: ooSQLite.1.0.0 ooSQLite.1.1.0 ooSQLite.2.0.0 and so on. If some one was using ooSQLite.2.0.0 and wanted to go back to 1.0.0, they could just go to SourceForge and download the ooSQLite.1.0.0 package. > * - if it is statically linked 'inside' your binary? Or are you allowing > a named DLL to be loaded by your interface code? Right now it is statically linked. In the future I might set up a build that links dynamically to the SQLite library. But, I don't see a big need for that at this point. The only advantage, to the user, would be if ooSQLite was stuck at version 3.2.0 of SQLite and the current version of SQLite was 3.55.0, then the user could upgrade the SQLite DLL on their system and be using the most current version of SQLite. I don't foresee that being the case at this point. If / when it becomes a problem, I'll make a version of ooSQLite that links dynamically to SQLite. And, I'll most likely set up a build that links dynamically to SQLite some time in the future when I don't have anything better to do. > I know from reading the SQLite users mail list - though I've not yet used > SQLite for anything - that some users also make custom builds of SQLite > themselves (see compile flags at http://www.sqlite.org/compile.html ). I > would expect that if someone was using a custom-built SQLite binary for some > application they'd want to be able to include it or build an equivalent into > an instance of the ooRexx SQLite package, if they wanted to use ooRexx as > part of that application. ooSQLite is very easy to build from source. The type of person that would have their own custom-built SQLite binary would simply check out the ooSQLite source and build their own version of ooSQLite. This option is always available, even if you don't want a custom build of SQLite. Just as /hex did, he built from source so he could try the online backup API before I had really even finished it. -- Mark Miesfeld ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
