← Back to team overview

kicad-developers team mailing list archive

Re: Failed installation

 

Karl Schmidt wrote:
Dick Hollenbeck wrote:
Dick
Currently, the internat directory in stable branch is the same as in docs repo. It can be deleted in the stable tree (in fact I did not noticed it was still in the stable branch until now).

This deletion has been done by me this evening.


Dick


I got an error complaining that /build/internat was missing while trying to build it under Debian - I've commented it out of the debian/rules file ... What was it for? Is it unneeded?

internat is not needed to my knowledge for an English user of Kicad. That directory holds the UI text translations and had been moved to a different repo branch, namely the "doc" branch. Your English is fine, you don't need it. :)


Please inform your debian package maintainer. I think there may be problems with his/her debian/rules file. In my opinion, he/she should find a way for it to trigger execution of CMake, and if this were to be done, then I don't understand why you should get this error, because the matching (i.e. most current) CMakeLists.txt file would not be looking for internat.

You have a problem with your aftermarket vendor (the debian package maintainer), and he/she needs your guidance. Base the build on CMake, don't care if something wraps this CMake (like debian/rules). But without CMake in the picture, we cannot help you here with build questions.

Currently there is a dependency on CMake 2.8.0 for latest revision, but if installing CMake 2.8.0 is grief for you and you can get 2.6 from repo, try editing the CMakeLIsts.txt file and finding and fixing the problem with 2.6 CMake. If you don't have CMake 2.6 from repo, then you are bound to install CMake 2.8 anyway by way of a direct download and build from the CMake.org website. Said differently, you have no prayer in getting CMake 2.4 to build Kicad, but by using 2.6 perhaps, and this is a subject of current discussion. Currently CMakeLists.txt requires 2.8.0, but this can be edited to find the problem, if any, with 2.6.

A path of least resistance might be to lobby for a 2.8 repo package of CMake from whomever controls that work, (debian CMake package maintainer).


Dick




Follow ups

References