On Tue, 25 Apr 2023 09:48:15 +0200 Tomaz Canabrava <tcanabr...@kde.org> wrote:

TC> My name is Tomaz Canabrava, I'm a Opensource developer mostly interested in
TC> contributing back to projects that I use.

 Hi Tomaz and welcome! I'm also an open source developer interested in
exactly the same thing, but this has somehow resulted me in maintaining
SOCI now :-/

TC> I forked a soci in github and I'm using version 4.0.3 to develop an
TC> application that should run in all major operating systems but it seems
TC> that the current mailine branch of soci has more modern CMake constructs
TC> than 4.0.3

 Unfortunately I don't know much about CMake and prefer to touch it as
little as possible. Thankfully there are other people who take care of it
in SOCI, mostly, but I'm afraid this means I won't be able to help you with
anything CMake-related.

TC> I had to hack around some issues that I found to be able to link Soci in
TC> linux / mac, as you can see in this patch. I also want to know if patches
TC> for 4.0.x are still accepted,

 Sure, I can merge PRs to 4.0, it's just that personally I don't have any
plans to work on it.

TC> if not, if it's safe to do a new release with current mailine branch or
TC> if the team needs help to finish what's needed for a new release.

 I really, really need to test the final version of the PR 954 and make a
new release once it's merged. But FWIW we do use current SOCI master in
production without any (known) problems, with multiple backends.

TC> But now on windows I'm having this issue:
TC> 
TC> error LNK2019: unresolved external symbol "struct
TC> soci::sqlite3_backend_factory const soci::sqlite3" (?sqlite3@soci
TC> @@3Usqlite3_backend_factory@1@B) referenced in function "public: bool
TC> __cdecl SociWriter::createOrOpen(class std::string const &)"
TC> (?createOrOpen@SociWriter@lvtmdb@Codethink@@QEAA_NAEBV?$basic_string@DU
TC> ?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)
TC> [C:\Project\Build\lvtmdb.vcxproj]
TC> 
TC> And I'm linking on all targets with:
TC>         Soci::Core
TC>         Soci::soci_sqlite3
TC> 
TC> (that are the names I exported via cmake ALIAS)
TC> 
TC> Any help is appreciated :)

 Are you using static or shared SOCI libraries? When using shared libraries
you shouldn't depend on this variable. When using static ones, it should be
found in the soci_sqlite3...

 Best regards,
VZ

Attachment: pgpQQbIB5sq9_.pgp
Description: PGP signature

_______________________________________________
soci-users mailing list
soci-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/soci-users

Reply via email to