wxWidgets Discussion Forum

Thank you so much, utelle. Your last answer shed absolute light on everything. But I have one last question :D Do I also need to create a debug BUILD for wxWidgets and wxSQLite3? I'm thinking NO on this, but I want to be sure I get everything right this time. Thank you. ***** UPDATE ***** I built wx...

I'm rebuilding xwWidgets and wxSQLite3. They're deleted from my drive and I'll build them new. But before I do, I need to know which makefile line to use for the wxWidget build. Which will be beneficial to also using wxSQLite3? Do I use: msw>mingw32-make -f makefile.gcc UNICODE=1 SHARED=0 and WX_SHA...

This is what I'm doing: I downloaded wxWidgets-3.1.3 ( not the pre-built binaries ) and went to config.gcc. There I changed two lines: # C compiler # CC = gcc CC = x86_64-w64-mingw32-gcc # C++ compiler # CXX = g++ CXX = x86_64-w64-mingw32-g++ This will provide me the 64-bit compilation, right? if so...

I downloaded wxSQLite3-4.5.1 and ran it as you said: C:\wxsqlite3\wxsqlite3-master\build>mingw32-make config=release_x32 "==== Building wxsqlite3 (release_x32) ====" Creating obj/x32/Release/wxsqlite3 wxsqlite3_version.rc sqlite3secure.c wxsqlite3.cpp Creating ../lib/gcc_lib Linking wxsqlite3 "==== ...

Thanks for your help, utelle. I have enough go to by so I think I'm going to blow up my wxWidgets and get the newest wxSQLite3 and make sure I have 64-bit builds. I might be back though

It didn't go very well: C:\wxsqlite3-3.3.1\build>mingw32-make -f makefile.gcc SHARED=0 WX_SHARED=0 MONOLITHIC=0 UNICODE=1 BUILD=debug if not exist ..\lib\gcc_lib mkdir ..\lib\gcc_lib g++ -c -o gccmswud\wxsqlite3_lib_wxsqlite3.o -DHAVE_W32API_H -D_UNICODE -D__WXDEBUG__ -D__WXMSW__ -IC:\wxWidgets-3.1....

I just downloaded a newer version of wxSQLite3 and tried this:
So frustrating.

I assume you have a wxWidgets shared build I don't. I didn't want the DLLs all over the place, so I set SHARED=0 for my wxWidgets. Do I need to recompile them to be shared? I made this change too: # The directory where wxWidgets library is installed WX_DIR ?= C:\wxWidgets-3.1.3 # WX_DIR ?= $(WXWIN)...

Since makefile.gcc got replaced with something I don't know how to work with in the newest release of wxSQLite3, I had to revert back to an older version. So I open my terminal and go to C:\wxsqlite3-3.3.1\build and type: C:\wxsqlite3-3.3.1\build>mingw32-make -f makefile.gcc SHARED=0 MONOLITHIC=0 UN...

PB: I guess I wasn't clear. Sorry for that. I said I got the same compiler as you. Here's the info from Windows: C:\Users\lands>gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=C:/MinGW/mingw32/bin/../libexec/gcc/i686-w64-mingw32/8.1.0/lto-wrapper.exe Target: i686-w64-mingw32 Configu...

Thanks, PB. I know just enough abt C++ to be 110% dangerous. Truth is, your last post showed me how to set the flags to ensure wxWidgets were compiled to use C++17 standards. So that was cool for me. But, it did me no good. Let me explain. I was using MinGW-w64 8.2.0. I tried all day yesterday to ge...

I'm not the expert here! I don't know if it's a bug or not! What do you think? I just told you all I did. Does it sound like a bug? Or something correctable, something that's been hammered on before?

I'm using Code::Blocks 17.12 and wxWidgets 3.1.2 using g++ 8.2.0. I created a new wxWidgets project in C::B and ran it. During the build process I got an error: ||=== Build: Debug in test-001 (compiler: GNU GCC Compiler) ===| C:\wxWidgets-3.1.2\include\wx\filefn.h||In function 'long long int wxFtell...

This compiler is rather outdated. I would strongly recommend to use a more recent version.

I actually have MinGW 8.2.0. But I had to resort to the MinGW 5.1.0 compiler that came with Code::Blocks to compile wxWidgets. So switching back now to the 8.2.0 compiler isn't going to break anything?

It's cool, doublemax. You tried. I just need to know how to Build wxSQLite3 so I can use it. I'll get the right information, eventually.