Hello, Thien-Thi Nguyen <[email protected]> writes:
> () Diogo F. S. Ramos <[email protected]> > () Thu, 10 Mar 2011 03:50:29 -0300 (BRT) > > I recently learn a technique where, during 'make', one 'cat' all the > sources files together, forming a big, single executable script. Doing > so, there is no need to install the .scm files, because they are all > inside the same executable file. > > This is the technique used in RPX: > > http://www.gnuvola.org/software/rpx/ > > It generalizes "compilation" from simple concatentation to include other > program-specific transforms. End result is two files to (un)install: > > - $(bindir)/rpx > - $(infodir)/rpx.info But then doesn’t it prevent code reuse? I don’t know to what extent this applies to RPX, but for instance, you can’t just ‘(use-modules (rpx the-feature-you-want-to-use))’; you end up doing ‘(use-modules (rpx))’ and potentially pulling more code than you really want. Thanks, Ludo’.
