http://www.mapleprimes.com/posts/99861-Creating-Compiled-Maple-Utilities en-us 2026 Maplesoft, A Division of Waterloo Maple Inc. Maplesoft Document System Tue, 09 Jun 2026 19:03:34 GMT Tue, 09 Jun 2026 19:03:34 GMT The latest comments added to the Post, Creating Compiled Maple Utilities http://www.mapleprimes.com/images/mapleprimeswhite.jpg http://www.mapleprimes.com/posts/99861-Creating-Compiled-Maple-Utilities http://www.mapleprimes.com/posts/99861-Creating-Compiled-Maple-Utilities?ref=Feed:MaplePrimes:Creating Compiled Maple Utilities:Comments#comment99864 <p>Really super, Joe. I mean that even more for showing everyone such nice clean techniques.</p> <p>I have a very minor variation to suggest, just to the installation location. Above you have it as,</p> <pre>installed_so := $(MAPLE_BIN)/$(shared_lib) installed_mla := ${HOME}/maple/lib/$(pkg).mla </pre> <p>That's maybe not ideal for everyone. The MAPLE_BIN directory might not be writable, if that is a network Maple installation. And someone might not want to tamper even in the slightest with the existing, nonempty folders of their Maple installation. And that `lib` location would require that the user's Maple sessions be configured so that `libname` included that location (either done manually each time, or in one's Maple initialization file).</p> <p>An alternative pair of installation locations might be,</p> <pre>installed_so := $(HOME)/maple/toolbox/pkg/bin.$SYS/$(shared_lib) installed_mla := ${HOME}/maple/toolbox/pkg/lib/$(pkg).mla </pre> <p>By bin.$SYS I mean setting SYS like the last part of kernelopts(bindir). The reason I suggest these is that I believe that modern Maple will automatically pick them up. Such directories/folders as maple/toolbox/foo/lib, under kernelopts(homedir), get automatically added to libname. And those bin.$SYS directories/folders automatically get prepended to LD_LIBRARY_PATH/PATH according to whether the OS is Windows/UNIX.</p> <p>Of course, you might decide that such automatic detection of binary+Library packages is something you <em>don't</em> want. But if you do, then these locations can be quite useful. Another neat twist is that the folders can be named like {$HOME}/maple/toolbox/13/pkg/lib/ and as such would get detected by Maple 13 but not by Maple 14. And so on.</p> <p>For some years now I've thought that it might be more generally useful if this functionality were documented explicitly. There are lots of packages on the Application Center which don't clearly explain how to alter libname and thus gain access to the commands in the bundled .mla Library archive. But a simple, general solution might be documentation which described re-usable locations for personal libraries (and any associated binaries) that would just work, automagically. Locations that were <em>not</em> the central `lib` or bin.$SYS location of the user's Maple installation itself, to avoid danger of clobbering anything crucial to Maple proper.</p> <p>Of course, many Application Center entries don't even use .mla archives at all, but merely provide their functionality in a bare worksheet. That's another issue altogether, to address another time.</p> <p>Back to the reusable location idea. One could stick more than one archive (and binary, if applicable) under one such folder. A single folder location could hold several such personal apps, as long as the .mla's had distinct filenames. (Or the apps could be merged into a single archive, if the package names were distinct. But that's more complicated, and gets away from the ease-of-use theme.) A common location could contains various add-on archives such as,</p> <pre> ${HOME}/maple/toolbox/misc/lib/pkgOne.mla ${HOME}/maple/toolbox/misc/lib/pkgTwo.mla </pre> <p>etc. That be much easier to explain, as far as where to place an Add-on .mla archive. "Just stick it in HOME/maple/toolbox/misc/lib" is a lot simpler than "Ok, place it anywhere, and then find your Maple initialization file, and then edit it and add the line libname:=...,libname".</p> <p>acer</p> The latest comments added to the Post, Creating Compiled Maple Utilities 99864 Sun, 05 Dec 2010 08:13:28 Z acer acer http://www.mapleprimes.com/posts/99861-Creating-Compiled-Maple-Utilities?ref=Feed:MaplePrimes:Creating Compiled Maple Utilities:Comments#comment99873 <p><a href="http://www.mapleprimes.com/posts/99861-Creating-Compiled-Maple-Utilities#comment99864">@acer</a> Thank you for the explanation.&nbsp; I was vaguely aware of Maple's ability to do this (automatically assign libname to read subdirectories under $HOME/maple/toolbox), but because I had customized my installation it wasn't working.&nbsp; However, I just straightened that out.&nbsp; Will probably have to clean up a number of scripts I have lying around, but this seems the right way to go.&nbsp; I've since modified the Makefile (both in the zip file and in the write-up) to install (no soft links) the generated Maple archive and shared binaries under $HOME/maple/toolbox/ListToolBox.</p> <p>I agree that this functionality of Maple should be clearly explained.&nbsp;</p> The latest comments added to the Post, Creating Compiled Maple Utilities 99873 Sun, 05 Dec 2010 11:46:38 Z Joe Riel Joe Riel