You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
singular creates saveral files of various different types (scripts, header, pkg config) that contain absolute paths to the installation directory and to the source directory.
See e.g.
polymake.app/Contents/Resources/bin/libpolys-config
polymake.app/Contents/Resources/include/singular/singularconfig.h
polymake.app/Contents/Resources/lib/pkgconfig/Singular.pc
I don't know whether they are actually used in an installed version of Singular. However,
we can't replace all the absolute paths with environment variables (e.g. in the headers). So the only solution I currently see is to write a post-installation script that replaces the paths with the correct ones on the target machine (triggered by the user (i.e. provide a "run once in a terminal" installation instruction) or via a check included in the start script (check one of the files, if wrong, run the script)).
This would fix paths to the installation directory. However, most files also point back to the build directory. This is a still unfixed bug in singular (http://www.singular.uni-kl.de:8002/trac/ticket/618), and we have no chance to fix it, the build directory is not included in the bundle.
Another solution would be to remove singular from the bundle...
The text was updated successfully, but these errors were encountered:
singular creates saveral files of various different types (scripts, header, pkg config) that contain absolute paths to the installation directory and to the source directory.
See e.g.
polymake.app/Contents/Resources/bin/libpolys-config
polymake.app/Contents/Resources/include/singular/singularconfig.h
polymake.app/Contents/Resources/lib/pkgconfig/Singular.pc
I don't know whether they are actually used in an installed version of Singular. However,
we can't replace all the absolute paths with environment variables (e.g. in the headers). So the only solution I currently see is to write a post-installation script that replaces the paths with the correct ones on the target machine (triggered by the user (i.e. provide a "run once in a terminal" installation instruction) or via a check included in the start script (check one of the files, if wrong, run the script)).
This would fix paths to the installation directory. However, most files also point back to the build directory. This is a still unfixed bug in singular (http://www.singular.uni-kl.de:8002/trac/ticket/618), and we have no chance to fix it, the build directory is not included in the bundle.
Another solution would be to remove singular from the bundle...
The text was updated successfully, but these errors were encountered: