./bootstrap
./configure --prefix=/opt/codeblocks-svn --with-contrib-plugins=all
make
sudo make install
I first used Jen's Debian repository to upgrade to 17.12 and encountered the error in wxWidgets:
"Fatal Error: Mismatch between the program and library build versions detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8),
and wxCore used 3.0 (wchar_t,compiler with C++ ABI 1011,wx containers,compatible with 2.8)."
... but building packages is not a viable solution at this time.What do you mean by this?
This process did allow CB 17.12 to run under Linux Mint 18.3 but as I suspected, I had to remove and reinstall filezilla and audacity.If you've used the wrong prefix then you've messed up your system. But this is not the default behaviour. The other way you can mess this up is you've built filezilla with another version of wxgtk. But then the fault is all yours.
IMO, this is not an acceptable process!Yes, this is why people use packages and learning how to make packages yourself is a good idea.
Someone with less experience would probably not completed this task and would have been left with a bad taste about CB and Linux in general.Then they'll learn to use packages or switch to either windows/osx/chromeos/whatever. It is not the end of the world anyway. Building code manually requires a lot of knowledge and persistence to always do the correct non-messing up thing and it is not for novices. I guess this is why things like docker and other container managers are popular now. They make it hard for you to mess systems up.
Further, I believe compiler dependency in widgets takes version control too far. This is probably something widgets needs to take care of. (I did see one post where the widgets developers were considering removing that in a future release, but I don't know if it has been done yet.)I don't have am idea what you're talking about.
This process did allow CB 17.12 to run under Linux Mint 18.3 but as I suspected, I had to remove and reinstall filezilla and audacity.I don't know what you did, but this should not be necessary and is a sign of that you screwed your system. Your system libraries all reside under
/usr
/usr/local
IMO, this is not an acceptable process! While I accomplished my result, I spent over 20 hours digging into the problem and researching how to overcome it. Someone with less experience would probably not completed this task and would have been left with a bad taste about CB and Linux in general.Linux != Windows
Further, I believe compiler dependency in widgets takes version control too far.This is actually a very good thing, without this instead of getting this error message you would get obscure, random runtime crashes which are extremely hard to debug. Even considerung the above point ;D.
i know for you this topic is closed. but me would interest why you used 3.1.2 and not the system default library, so you do not have to uninstall filezilla and audacity...