User forums > Nightly builds
The 13 August 2022 build (12864) is out.
gd_on:
Those lines :
--- Quote --- <MakeCommands>
<Build command="" />
<CompileFile command="" />
<Clean command="" />
<DistClean command="" />
<AskRebuildNeeded command="" />
<SilentBuild command=" > $(CMD_NULL)" />
</MakeCommands>
--- End quote ---
are not in my codeblocks_windows.cbp. Of course, they are not necessary.
More, the line :
--- Quote --- <Option compiler="gnugcc_x64_compiler" />
--- End quote ---
is not in the standard CodeBlocks_wx32_64.cbp (it's simpy gcc, as in mine).
So, you have modified the provided cbp (automatically, intentionally or not, ... I don't know).
I think that <option compiler="gcc" /> line refer to the default compiler in C::B. So, if it is correctly set for 64 bits set (in my case gcc, g++ in C:\msys64\mingw64\bin) (or 32 bit set for 32 bit build), cbp should work as they are, without modifying them.
Nevertheless, I have found a small problem in my previous cbp : for exchndl, the path win64 was still hard coded. Here is a modified version which should be better for 32 bits only build.
Frank_CB:
@gd_on:
My heartfelt apologies! I never intended to infer that your Codeblocks_Windows.cbp file had any unnecessary code in it. I checked what you downloaded (Cbps_3.7z) and found no extra code in Codeblocks_Windows.cbp. I certainly didn't add it to your Codeblocks_Windows.cbp before using it. The only thing I changed was the compiler which I have always used for 64-bit builds. I don't have a "gcc" selection for a compiler. I suppose i could copy gnu/gcc and name it gcc (a late thought).
The Codeblocks_wx32_64.cbp was copied from my Codeblocks_wx31_64.cbp It used the compiler I have always used 64-bit builds. That compiler was copied from the gnu/gcc compiler and had it's toolchain correctly updated (C:\Mingw64).
When I go through building a 64-bit build the first time a new version of wxWidgets comes out I have to change the compiler and set wx-cfg to 64 for the core. Then for the ContribPlugins I need to step through each plugin or contributed plugin and change the compiler and wx_cfg. I also have to re-arrange the search directories order to place the directory containing setup.h first. A time consuming project. Subsequent builds, as long as wxWidgets version doesn't change, are a breeze. There might be a more efficient way to do it, but since it's a hobby, i'll continue.
Regards
Frank_CB:
@gd_on:
Am attempting to use Codeblocks_Windows.cbp. Any idea why these two include directories ( -I.objs32_64\include and -I. ) are showing up in the build log, but aren't defined anywhere else, that I'm aware of? The 64-bit build runs fine until it fails in scintella because it couldn't find wxprec.h. The include directory statement that defines where setup.h is now in position 3 instead of position 1 (wxWidgets stipulation for 64-bit builds).
Have created a compiier that i'm calling "GCC" and set it up to be 64-bit.
Regards
gd_on:
As far as I understand, the problems you describe should also happen with standard *32_64.cbp versions. If you compare line by line *32_64.cbp versions and *windows.cbp versions you can see that only names are buillt with global variables instead of hardcoding 32, 64 and 32_64.
So, -I.objs32_64\include and -I. are also used by standard 32_64 (and even 31_64) versions. In particular, .objs32_64\include is a directory where precompiled headers *.gch are stored.
The order of lines are not changed, as far as I remember.
For wxprec.h, I have no explanations. Your statement :
--- Quote ---The include directory statement that defines where setup.h is now in position 3 instead of position 1
--- End quote ---
is not precise. Where did you see that ?
I have not created a specific "GCC" but I simply use the standard "GNU GCC Compiler" as my default compiler, but with fields set with path and names of my 64 bits used compilers.
Frank_CB:
@gd_on:
Your correct, those two extra includes are in both *wx32_64.cbp and *World.cbp. That definitely throws a monkey wrench into my practice, when creating 64-bit builds, of re-arranging the order of include directories for the compilers to insure that the directory that contains setup.h is first. I've been doing that for at least 10 years. I cannnot recall where I read that requirement? It works for *wx32_64.cbp, but not for *World.cbp. I'm at a loss as to what is causing that. i just hope that the other four individuals that downloaded your cbps_3.7p are having better success.
Have you successfully built 32-bit and 64-bit versions of Codeblocks from your modified cbps? I assume that you have.
I am attaching a zipped file that contains build logs and build messages for both *wx32_64.cbp and *World.cbp.
Regards
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version