in script postinst I drive ld.so.conf as the final step:Ĥ. I install a version file as "/etc/brlcad/version" with contents like:ģ. Non-versioned method you use (per Debian policy).Ģ. But I'm going to change back to the standard, Currently I modify the system to install BRL-CAD in a versionedĭirectory. My changes (for a special project with some hacky customization):ġ. > I'm curious to knowing the changes you made on deb building process. > There are at least three basic things to make brlcad deb to accomplish with Debian rules: Their differences are smaller that they seems. I'm curious to knowing the changes you made on deb building process.Īnyway, I think that any improve/change applied to deb packages must be applied to rpm too. do not include any shared library that is already present on the system There are at least three basic things to make brlcad deb to accomplish with Debian rules: > (such as possibly having a separate deb dir for Debian). > coordinate some changes with Jordi if I do become a Debian packager > for my Debian-using clients, so that I would probably want to > for my own purposes for practical use in producing a suitable package > I also note that I have changed the current BRL-CAD deb process a bit ![]() > The list and status of Debian supported architectures can be seen on > developers is that it would get good testing on several architectures. If you have any further recommendations of what I should try when I'm ready to come back to this, they would be very much appreciated.Ĭabernet: thanks for the suggestion, I'll definitely have a look at that too.> I am considering volunteering to be BRL-CAD package manager for Debian I'm still getting used to working on and navigating a Linux system, so maybe I should wait until I have a better idea of what's going on before I try and tackle BRL-CAD. I think perhaps I've tried to jump in at the deep end. I copied the brlcad directory to /usr and used the absolute path as you said, but still the same problem. You probably need to either set your LD_LIBRARY_PATH (via something like "export LD_LIBRARY_PATH=/path/to/brlcad/lib:$LD_LIBRARY_PATH") to point to BRL-CAD's "lib" directory where libtermio.so and friends reside, or better - move the "brlcad" directory that you unpacked into to your /usr directory. The binary distributions expect to be installed into /usr/brlcad so if you just unpacked the tarball without copying the files into place, then the binaries aren't going to be pointing at the right run-time path. If you don't want to set your PATH, you can give an absolute path such as "/usr/brlcad/bin/mged" instead. You shouldn't cd to the bin directory as that will potentially just be more confusing down the road. Similarly, running "./mged" implies that you didn't update your PATH variable to include BRL-CAD's "bin" directory. Does anyone have an idea what could be going wrong here, or what I could try to fix it?The binary distributions expect to be installed into /usr/brlcad so if you just unpacked the tarball without copying the files into place, then the binaries aren't going to be pointing at the right run-time path. I downloaded the binaries (release 7.10.4), extracted them using tar and tried to run the program by cd-ing to the relevant directory in konsole and typing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |