User forums > Help

Installing Code::Blocks from source on Linux

<< < (3/7) > >>

Krice:
In some unrelated projects people have solved this by creating a symlink to libtiff which in this case is libtiff.so.6.0.2 (other files are symlinks themselves) so I did that in my usr/lib64, but now it's just giving an error already in the compile phase, in astyle.h:


--- Code: ---In file included from asstreamiterator.h:15,
                 from asstreamiterator.cpp:10:
/usr/include/astyle.h:295:44: error: 'std::string_view' has not been declared
  295 |         const std::string* findHeader(std::string_view line, int i,
      |                                            ^~~~~~~~~~~

--- End code ---

This seems to indicate that something doesn't include std::string header, right?

Edit: also, there could be some kind of confusion in including astyle.h in asstreamiterator.h. If you use angle brackets it's trying to find the file in usr/library while there is also plugins/astyle/astyle directory where you can find another astyle.h which is not included unless you write #include "astyle/astyle.h", well I guess depending how this project is handling that kind of stuff, could be something else happening.

SharkCZ:
You can get the latest nightly C::B for Fedora from https://copr.fedorainfracloud.org/coprs/sharkcz/danny/. As for the build procedure you can take a look at the spec file, it shows what package you need to have installed and what commands to run, see https://src.fedoraproject.org/rpms/codeblocks/blob/rawhide/f/codeblocks.spec

Krice:

--- Quote from: SharkCZ on March 17, 2025, 04:30:29 pm ---it shows what package you need to have installed
--- End quote ---

Am I supposed to know how to read that? I think compiler errors could also hint that wxWidgets is missing, but it should be installed... Maybe I could try to write a wx program to see if it works. Anyway, how is this so difficult? I think this is more difficult than when I tried to compile Code::Blocks in OSX and that was a journey.

stahta01:

--- Quote from: Krice on March 18, 2025, 07:18:36 pm ---
--- Quote from: SharkCZ on March 17, 2025, 04:30:29 pm ---it shows what package you need to have installed
--- End quote ---

Am I supposed to know how to read that? I think compiler errors could also hint that wxWidgets is missing, but it should be installed... Maybe I could try to write a wx program to see if it works. Anyway, how is this so difficult? I think this is more difficult than when I tried to compile Code::Blocks in OSX and that was a journey.

--- End quote ---

The [linking] error posted implied wxWidgets was from an local build instead of being an Linux Distro package.
Did you build it recently? If yes, I have nothing to suggest. If no, I suggest building it again and see if the error changes or goes away.
And, the posting the reason you did the local build of wxWidgets might help people to help you.

Tim S.

Krice:
I could have compiled wx from source but there was no source directory. Downloaded wx source, ran configure and then make uninstall. But it doesn't help. I think it did remove something from usr/local/lib, but it left wx directory with another empty wx directory at the end of it. wx can be also found from usr/lib64 and /lib64. How does it confuse compiler if it's installed in those locations, shouldn't the compiler choose one and not mix them, which could cause some problems? At this point I probably have to delete package wx, see if anything is left and delete those files manually, then reinstall it. Right? F-- linux...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version