User forums > General (but related to Code::Blocks)
c++11
mistar:
--- Quote from: oBFusCATed on October 11, 2013, 11:35:12 am ---
--- Quote from: frithjofh on October 11, 2013, 11:30:23 am ---I wanted to know for c::b itself, its code, its plugins...
--- End quote ---
No, until all major long-term-support linux distros switch to GCC 4.7 at least.
Or to make it a bit more clear: When there is a RHEL/CentOS that uses GCC 4.7 as its native compiler and I've this distro installed on my work machine.
I've just switched to the latest CentOS and the compiler is GCC 4.4, so you're out of luck:)
Until then I'll revert all C++11 commits :)
--- End quote ---
It is possible to add C++11 code to C::B sources with
--- Code: ---#if (__cplusplus >= 201103L)
// C++11 code goes here
#else
// old code here
#endif
--- End code ---
and everybody would be happy...
oBFusCATed:
--- Quote from: mistar on October 14, 2013, 03:52:52 pm ---and everybody would be happy...
--- End quote ---
And what is the benefit if we have to maintain both versions?
The idea of switching to C++11 is to make it easier to write and maintain C::B, so this will defeat the purpose of the switch.
killerbot:
there are ways to install more recent gcc on centos and family.
oBFusCATed:
--- Quote from: killerbot on October 14, 2013, 06:20:45 pm ---there are ways to install more recent gcc on centos and family.
--- End quote ---
This doesn't change anything, because they won't be the system compiler!
And would require hacking the LD_LIBRARY_PATH or using rpath for the libstdc++.so,
which will make using C::B on CentOS a nightmare and people won't do it.
Also it will be a nightmare to support on the various older Ubuntus...
p.s. from my tests GCC 4.6 is not a C++11 compiler one can depend on. GCC 4.7 is the first one.
ptDev:
--- Quote from: oBFusCATed on October 14, 2013, 06:30:21 pm ---
--- Quote from: killerbot on October 14, 2013, 06:20:45 pm ---there are ways to install more recent gcc on centos and family.
--- End quote ---
This doesn't change anything, because they won't be the system compiler!
And would require hacking the LD_LIBRARY_PATH or using rpath for the libstdc++.so,
which will make using C::B on CentOS a nightmare and people won't do it.
Also it will be a nightmare to support on the various older Ubuntus...
p.s. from my tests GCC 4.6 is not a C++11 compiler one can depend on. GCC 4.7 is the first one.
--- End quote ---
I remember seeing a while back a program that was distributed as single packed archive that even contained its own version of libstdc++ and a number of system shared objects, so it is possible to provide a custom build that is not based on the system libraries, it will just prevent one from using debian packages or rpms, but it still is possible at the expense of a rather bloated binary distribution.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version