User forums > Nightly builds
The 13 August 2022 build (12864) is out.
Frank_CB:
@gd_on:
If I read what you downloaded correctly, you have it setup for a 32-bit build using a particular 32-bit compiler. Have you given any thought to being able to use any 32-bit/64-bit compiler?
Regards
stahta01:
--- Quote from: Frank_CB on August 20, 2022, 09:55:16 pm ---@gd_on:
If I read what you downloaded correctly, you have it setup for a 32-bit build using a particular 32-bit compiler. Have you given any thought to being able to use any 32-bit/64-bit compiler?
Regards
--- End quote ---
Do you have any reason to believe what you posted?
The only 32 I found was for wxWidgets 3.2 the stuff I found used 64 for osbits.
So, what are you talking about if it is not "Cbps_3.7z" in https://forums.codeblocks.org/index.php/topic,25068.msg170872.html#msg170872 ?
Tim S.
gd_on:
my cbp are not so different than standard ones. This work, based on Andrew Cotrell's one, try to avoid some hard coding settings.
Main differences are in folder name build which are initialised with global variables instead of beeing hard coded.
May be the major diference for 32 bit build is : for example with wxWidgets 3.1, the forder name with standard build are .objs31 and devel31, and with my cbp they are .objs31_32 and devel31_32, following the same logic than for 64 build names.
Also, compilation option -m32 or -m64 is built according to the global variable cb_build.osbits. The same for the name of the used wxwidgets libraries.
The compiler is simply gcc (as in standard build). So it's the 1st compiler found in your system path : it may be 32 or 64 bits, depending of your path settings order.
Frank_CB:
@gd_on:
Currently building a 64-bit version of SVN 12877, using re-named and up-dated versions of Codeblocks_wx31_64.cbp and ContribPlugins_wx31_64.workspace. The plugins' cbp and update*.bat (if provided) files were also re-named and up-dated.
However, prior to using my cbp and workspace files, I placed the files you provided in cbps_3.7z into the proper directories and updating my global variables. Attempting to use your Codeblocks_Windows.cbp and codenlocks_Windows.workspace resulted in errors preventing the build to start. Couldn't seem to find the compiler. No changes made to oolchain.
Any idea what's cauings this behavior?
Regards
Frank_CB:
@gd_on:
The code at the start of Codeblocks_Windows.cbp and Codeblocks_wx32_64.cbp
--- Code: ---?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
<FileVersion major="1" minor="6" />
<Project>
<Option title="Code::Blocks Windows" />
<Option default_target="src" />
<Option compiler="gcc" />
<MakeCommands>
<Build command="" />
<CompileFile command="" />
<Clean command="" />
<DistClean command="" />
<AskRebuildNeeded command="" />
<SilentBuild command=" > $(CMD_NULL)" />
</MakeCommands>
<Build>
=======================================================================
?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
<FileVersion major="1" minor="6" />
<Project>
<Option title="Code::Blocks wx3.2.x (64 bit)" />
<Option default_target="src" />
<Option compiler="gnugcc_x64_compiler" />
<Build>
--- End code ---
The Make commands in your .cbp Throw me. Are they necessary?
Regards
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version