User forums > Using Code::Blocks
64bit programs in backtics?
cacb:
Hi,
I have been using the MSVC compilers with Code::Blocks on Windows for quite some time. Recently I began upgrading to Visual Studio 2013 compilers. This now seems to work, I am able to build both x86 (32bit) and x64 (64bit) program under Code::Blocks with the MSVC compilers. For x64 I am currently using the x86_amd64 cross compiler toolset in Visual Studio 2013 Express.
My project setups use the "backtick" feature, for example under under Project Options -> Compiler settings -> Other compiler options, I have things like this (notice the backticks):
`$(CPDE_USR)\bin\wx-config.exe --prefix=$(#wx) --wxcfg=$(#wx.release) --cxxflags`
wx-config.exe is a program compiled by me. When it is compiled using the x86 toolset everything works as expected, but when compiled using the x86_amd64 toolset it does not appear to run in the backtic context, i.e. no output at all. When tested on the command line there is no problem.
I am running the pre-compiled Nightly Build svn 10503 undet Windows 7 http://forums.codeblocks.org/index.php/topic,20676.0.html
Is there anything to prevent 64 bit programs to run in backtics?
stahta01:
I would guess a 32 bit program (Code::Blocks) has issues running a 64 bit program.
Tim S.
cacb:
--- Quote from: stahta01 on November 08, 2015, 04:12:46 am ---I would guess a 32 bit program (Code::Blocks) has issues running a 64 bit program.
Tim S.
--- End quote ---
That was my initial guess too. I guess your guess is a confirmation :P
If so, how exactly are programs called in the backtick context? Is it for example any different from how the compilers/linkers are called? I mean, is it likely to be a problem to use (from Code::Blocks) the native amd64 toolset found in MSVC 2013 Professional? It was my plan to do so on another machine.
If we can't run 64bit tools (including native 64bit compilers) from within Code::Blocks (32bit), is there a 64bit build of the Windows nightlies somewhere? If not, perhaps it could be an idea for an upcoming release.
Jenna:
The function is in sdk/globals.cpp:837 .
It calls wxExecute and caches the output, on windows it's run through "cmd /c " on other platforms it runs directly.
So this is most likely an issue with wxExecute .
oBFusCATed:
Is there any error printed somewhere? Does you program depend on some dll? If it does could it be that when run from inside cb it is not found?
Navigation
[0] Message Index
[#] Next page
Go to full version