User forums > Using Code::Blocks
Suppress the default compiler selection window from cmdline args ?
asivakum:
Is there anyway to suppress the default compiler selection window from commandline ?
When the build is launched from a proprietary build framework, I see that the codeblocks window is stuck and not continuing with the compilation.
We suspect that the compiler option selection window pop-up is preventing this.
As its an automated build environment, we cannot login to that machine and confirm the compiler selection.
Is there any way to auto confirm the pop-up windows from cmd line args ?
BlueHazzard:
--- Quote ---We suspect that the compiler option selection window pop-up is preventing this.
--- End quote ---
In your last post you say that the build is finished, so it is unlikely this window...
--- Quote ---Is there any way to auto confirm the pop-up windows from cmd line args ?
--- End quote ---
At the moment sadly not. I will happily apply any changes to fix it if we find the exact window that causes your problems....
asivakum:
--- Quote from: BlueHazzard on May 31, 2021, 08:43:22 am ---In your last post you say that the build is finished, so it is unlikely this window...
--- End quote ---
Thanks for your support.
Yes, thats true. However, we reinstalled codeblocks in the build server to check if there is any issue, and I guess after that we are seeing that the output binaries are not yet generated.
So, I triggered a build from my user login and found that its asking for confirmation of compiler settings for few compilers("Change in compiler settings detected, do you want to retain it to old settings"- I am not sure of the exact wordings, as I did not take a screenshot.) and a pop-up window to choose the default compiler.
Hence, I assume these are the pop-ups thats preventing the build.
BlueHazzard:
We really have to output more information in the console for batch builds....
do you have the possibility to build codeblocks by yourself, so we can test new implementations in your environment?
In the mean time, to speed things up:
1) Create a codeblocks installation on your local machine, that has the same paths as on the build server
2) Try to make your projects build on your local machine
3) If everything works, copy the configuration file from your local machine (found in C:\Users\USERNAME\AppData\Roaming\Codeblocks\default.conf to the same path of the build server
then it should work...
asivakum:
--- Quote from: BlueHazzard on May 31, 2021, 11:30:59 am ---We really have to output more information in the console for batch builds....
do you have the possibility to build codeblocks by yourself, so we can test new implementations in your environment?
In the mean time, to speed things up:
1) Create a codeblocks installation on your local machine, that has the same paths as on the build server
2) Try to make your projects build on your local machine
3) If everything works, copy the configuration file from your local machine (found in C:\Users\USERNAME\AppData\Roaming\Codeblocks\default.conf to the same path of the build server
then it should work...
--- End quote ---
Thanks a lot for this suggestion. This worked perfectly, and I see my build has passed now.
Thanks very much for your support.
Navigation
[0] Message Index
[#] Next page
Go to full version