Greetings, Statalist,
I am wrapping libsvm for Stata, and I have hit a snag. I would like to bundle libsvm with my wrapper on Windows and OS X to make a one-step installation. I discovered the .pkg "g PLATFORM path install_name" command, which should let me distribute the bundled files as appropriate per platform, but I discovered that the only files Stata considers part of the package (and what it installs when you do "net install") are ones with these extensions
Also even if I did convince Stata to download the DLL, it will get put into the adopath, which is not the system library path. So I am obviously going about this the wrong way.
I can think of three options, don't like any of them, and I'm looking for suggestions:
I am wrapping libsvm for Stata, and I have hit a snag. I would like to bundle libsvm with my wrapper on Windows and OS X to make a one-step installation. I discovered the .pkg "g PLATFORM path install_name" command, which should let me distribute the bundled files as appropriate per platform, but I discovered that the only files Stata considers part of the package (and what it installs when you do "net install") are ones with these extensions
Code:
.ado .class .dlg .hlp .idlg .ihlp .jar .key .mata .mlib .maint .mnu .pdf .png .resource .scheme .plugin .stbcal .sthlp .style
I can think of three options, don't like any of them, and I'm looking for suggestions:
- statically link libsvm
- distribute libsvm as, say, libsvm.resource, rename it on first run to libsvm.dll or libsvm.dylib as appropriate, using Stata's command, and either
- load it with dlopen()
- somehow edit the system library path (PATH on Windows, DYLD_FALLBACK_LIBRARY_PATH on OS X) to include the adopath
Comment