Download Mingw Codeblocks [BEST]
Coleman John
NOTE: The codeblocks-20.03-setup.exe file includes Code::Blocks with all plugins. The codeblocks-20.03-setup-nonadmin.exe file is provided for convenience to users that do not have administrator rights on their machine(s).
CodeBlocks is an open-source, cross-platform (Windows, Linux, MacOS), and free C/C++ IDE. It supports many compilers, such as GNU GCC (MinGW and Cygwin) and MS Visual C++. It supports interactive debugging (via GNU GDB or MS CDB). CodeBlocks is surprisingly versatile, and in my opinion, much better than the Visual Studio suite. The mother site of CodeBlocks is www.codeblocks.org.
Goto Click "Download the binary release". Select your operating platform (e.g., Windows 2000/XP/Vista/7). Download the installer with GCC Compiler, e.g., codeblocks-13.12mingw-setup.exe (98 MB) (which includes MinGW's GNU GCC compiler and GNU GDB debugger).
x86_64-w64-mingw32-g++.exe -LC:\SDL2-devel-2.0.4-mingw\SDL2-2.0.4\lib\x64 -o bin\Debug\Tutorial1.exe obj\Debug\src\Main.o -lSDL2 -lSDL2main
C:\SDL2-devel-2.0.4-mingw\SDL2-2.0.4\lib\x64/SDL2.lib: error adding symbols: File in wrong format
collect2.exe: error: ld returned 1 exit status
Process terminated with status 1 (0 minute(s), 1 second(s))
1 error(s), 0 warning(s) (0 minute(s), 1 second(s))
this is the first time I am trying to create an VST.
I am trying to build an empty codeblocks project compiled with mingw, but I am not able to create it with VST3 project generator. The output is this:
Dear Berak , Thanks . I have both downloaded available with me. VS2010 and Mingw almost 1.3 GB data , Got MinGW through mingw-get-setup.exe , have cmake-3.0.0-win32-x86.exe , I also have downloaded MinGWStudioFullSetupPlus-2.exe . I have used codeblocks-10.05mingw-setup.exe to install CodeBlock. I have also tried C::B ver 12 and codeblocks-13.12mingw-setup.exe
You are making it way to complex ... right click on your codeblocks project, build options, click drop down menu. Is there a visual compiler 2008? or a visual compiler 2010? If not, just download that one and it will work.
Ok, sorry. Changed to x86_64 mingw. Sill the same problem. My g++ is 64, all of my so are 64, still wrong format.
This only happens with those I need libraries. For a simple Hello World, no error, and .exe is created.
Even .so files in usr/lib64 won't work. So you are saying, I have to link to dll files, instead of those .so files ?
The mingw compiler handles this for you for the standard libraries, that's why your hello-world example worked fine. But as soon as you include other libs, you need to give the linker the path to the dlls. In most cases you can use mingw's pkg-config to help with this, so just like in a linux build you could specify LDFLAGS from `pkg-config --libs ` you can use mingw's pkg-config the same way. I forget the exact path and name of mingw's pkg-config but it follows similar naming conventions as the compilers.
1) The mingw group in the AUR, or the mingw repository. I don't see fltk there though, so you might need to build that yourself. See any of the hundreds of other mingw PKGBUILDs for a template on how to build it. But in general, installing dependencies for mingw builds is just like installing dependencies for linux builds. If you'd build a package for linux using gcc and libABC, then to build for windows you'd need mingw-gcc and mingw-libABC. You cannot mix and match: your libraries must match the system targetted by the compiler.
2) The dlls are the windows equivalent of .so files, you should not need to "generate" them, they are in the mingw packages for that lib - fltk again may be an exception, but you don't need to do anything special to generate the dlls, just build and install a mingw fltk package. A makefile alone cannot generate anything, but a makefile with a mingw cross compiler does compile for windows, that's it's whole purpose.
I can't give a complete step-by-step as I'm no longer cross compiling on this system, but frankly I think you may need to take a step back and start a bit smaller. Use libs that are available already for mingw to get used to cross compiling. Then once you get used to it, making PKGBUILDs for other libs like fltk will be trivial. You could also just download the windows dlls from fltk's upstream source and just drop them in your build directory - but this would seem a bit messy to me. EDIT: maybe not, fltk does not seem to distribute a windows build from what I can (quickly) find, just the source code.
You are using a compiler that produces 64-bit binaries (x86_64-w64-mingw32-g++.exe) so you need to use 64-bit GLFW library files. These are in lib-mingw-w64 in the 64-bit binary archive.
I have similar problems in codeblocks but that is most likely my fault and havent spent nearly as much time on that as I did trying to make it work in Visual Studio 2019, Visual Studio code, and QT. I am a newb but the Win SDK error and the depreciated code errors seems to point to a change in the latest VS19.
The only other changes were to make sure that codeblocks set the right path for the install and removed remnants of other settings that had somehow included themselves. The debug build config still doesnt work only the release so there must be some other stuff left behind.
Please note that this is CodeBlocks without the bundled mingw compiler. I have the msys compiler with both 32 and 64 bit versions of mingw installed in c:/msys/mingw64 which is the one I want to use. It is tested and works fine with CodeBlocks when selected.
df19127ead