Hi Udon, to come to an possibly productive end here: if you think an amd64 compilation would be useful to you (I do doubt that though :(, drop me a note and I will fire up a compiler run on one of my servers, and tar the results.
/eno > > @eno > I'm sure RPMs are really cool. But previously I just included all the dynamic > libraries in a directory so LabVIEW knew where to find them and everything > worked fine. The end user just unzipped the API to a directory and started > developing. No "download this, then do that" or "oh and by the way you need > this > and also that is a dependency". Simple for the end-user and for me (I just > need > to zip a directory). From what people tell me, unlike the MAC, SQlite isn't > part > of any default install in linux and they would have to do as you suggest and > download something (and I would have to support that installation too-which I > cannot). Additionally, thAny solution that involves linux is really off the > menu. It needs to be a cross-compile or I just drop linux support. But at > least > I can then say I have made an effort for linux users - even though I'm not > one > myself. > > The platform is whatever the SQLite from sqlite.org was compiled for > (preferably > with the aforementioned switches, but if that's too hard; then with default). > The windows and VX works libraries have those defines, but if it's not > possible, > then linux users won't get full text search and they'll have to use low level > functions (rather than the easy API) for foreign keys. They'll just have to > live > with it as a limitation in linux as MAC users do. > > Regards > Udon _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
