User forums > Using Code::Blocks
Compiling C::B using Msys2
alle_meije:
I use the '--enable-monolithic' option because on the install-from-source-in-windows page http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows it suggests that you set MONOLITHIC=1 in the file Makefile.gcc --which does not seem to be in the distribution any more.
All to no avail... Still exits with the static data member error.
In the meantime I'm using http://downloads.sourceforge.net/project/codeblocks/Binaries/Nightlies/2015/CB_20150604_rev10320_win32_setup.zip and save often (-:
stahta01:
--- Quote from: alle_meije on August 19, 2015, 01:47:51 pm ---
Is this something that should be set explicitly when (in Windows) it's not possible to use C::B to build C::B?
--- End quote ---
Yes, you can use CB to build CB in both Windows and Linux.
Edit: The only thing I remember that needs set is the CB Global variable of "cb_release_type" needs set to "-g" or " " (single space) without the double quotes.
Tim S.
stahta01:
I was able to duplicate the error using wxWidgets 3.0 branch and MSys2.
This likely means that there is a problem using MSys2 and Code::Blocks configure/make method of building Code::Blocks.
I might try to find the cause of the problem in the future.
Future problems, I saw during attempt.
The use of option "-ansi" will cause a windows build to fail once it gets far enough.
Note: I did see a patch in the past to patch the configure/make for Windows (it was before MSys2 likely existed)
The method of Building on Windows has always been using the CB Project file instead of configure/make.
Therefore, it is NOT worth reporting this as a official bug; but, is worth reporting a patch to fix the issue.
I do NOT know enough about the CB configure/make build system to attempt a patch at this time.
There was a CB thread on using Cygwin to build CB using configure/make.
I posted in it; it might have info useful for trying to build under MSys2.
Tim S.
alle_meije:
Many thanks for the effort! I do much appreciate it.
If I can help in any way to make this work then I'm nore than happy to.
It did not seem to me like a (coding) bug -- most likely a difference in how to fit into the host system.
As mentioned before, Msys2 is a bit of both in that respect. Windows binaries in a Linux-style shell.
My secret hope was that if C::B can be built using regular make, aclocal etc then it can become an Msys2 package
(Msys2 uses the 'arch' linux package management system, which is easier than a windows installer or Chocolatey)
For developing C::B itself, using an already-existing existing copy seems logical, but in Msys2 there is no such copy.
I will read the cygwin thread, thanks!
That would be this one?
http://forums.codeblocks.org/index.php/topic,18525.0.html
The OP also has problems with importdll.
stahta01:
--- Quote from: alle_meije on August 24, 2015, 03:04:46 pm ---I will read the cygwin thread, thanks!
That would be this one?
http://forums.codeblocks.org/index.php/topic,18525.0.html
The OP also has problems with importdll.
--- End quote ---
Yes that was the thread.
I think a build under cygwin might be a way to boot-strap an CB that works under MSys2; but, this is just a guess.
The clearly better way for CB is for the configure make to work under MSys2.
Tim S.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version