Il giorno ven, 01/07/2022 alle 18.15 +0100, James Crake-Merani ha scritto: > Hello, > > I was just wondering what approach people tend to take when writing a > script which installs a module onto the load-path. I understand this > path might be different on different machines so how do you make sure > the module is installed in the right path? Would you use something > like a Makefile?
not only a Makefile The whole Autotools chain There are 2 options: 1) you write the config.am and Makefile.am (or however they're called) by hand and you deal with the Autotools directly, by hand 2) You use guile-hall and it will wrap the Autotools making the experience a bit less frustrating BUT I wonder: why you want to install your module ? You might want to distribute it as a simple handful of source files Guile will compile it automagically at need If your module has no dependencies, that could be an easy option If it _has_ dependencies, then the Autotools might be of help Did you think about this ? I hate to second guess your question I understand it might be perceived as rude and I'm sorry for that I just think these distinctions in use cases are not clear at all, in the manual and in general So this could be an easy pitfall