callable

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
callable [2019/02/11 21:18] – external edit 127.0.0.1callable [2021/01/12 15:38] (current) – external edit 127.0.0.1
Line 35: Line 35:
  
 Methods: Methods:
-  * ''%%prefer_now("label")%%''  corresponds to the [[::general#preferences|interactive command]] of the same name.+  * ''%%prefer_now("label")%%''  corresponds to the [[user_guide:howto:shell_custom#preferences|interactive command]] of the same name.
   * ''%%set_custom("name", value)%%''  temporarily changes the value of the given custom variable, until the Scope object is destroyed.  Custom variables are specified in the same manner as in corresponding ''Main::set_custom'' methods.   * ''%%set_custom("name", value)%%''  temporarily changes the value of the given custom variable, until the Scope object is destroyed.  Custom variables are specified in the same manner as in corresponding ''Main::set_custom'' methods.
  
Line 42: Line 42:
 ==== Building a program ==== ==== Building a program ====
  
-You can use polymake callable library for building your programs only after having installed it at the final destination, that is, after ''make install'' .  To facilitate the build process, polymake comes with a small utility ''polymake-config'' which resides side by side with the main script ''polymake'' in the binary installation directory.  Calling this utility with various options you can obtain the compiler and linker options needed for successful build of your program.  You can even insert the calls in your Makefile directly, using the GNU make ''$(shell)'' function or `backtick` shell substitution.+You can use polymake callable library for building your programs only after having installed it at the final destination, that is, after ''ninja install'' .  To facilitate the build process, polymake comes with a small utility ''polymake-config'' which resides side by side with the main script ''polymake'' in the binary installation directory.  Calling this utility with various options you can obtain the compiler and linker options needed for successful build of your program.  You can even insert the calls in your Makefile directly, using the GNU make ''$(shell)'' function or `backtick` shell substitution.
  
 Following configuration parameters can be requested from ''polymake-config'': Following configuration parameters can be requested from ''polymake-config'':
Line 59: Line 59:
 You can add an option ''%%--debug%%'' before ''%%--cflags%%'', ''%%--ldflags%%'', or ''%%--libs%%'' if you are going to debug your program together with polymake.  Compiler options displayed without ''%%--debug%%'' provide for a build optimized for execution speed. You can add an option ''%%--debug%%'' before ''%%--cflags%%'', ''%%--ldflags%%'', or ''%%--libs%%'' if you are going to debug your program together with polymake.  Compiler options displayed without ''%%--debug%%'' provide for a build optimized for execution speed.
  
-For compilation with debugging enabled run ''%%make Debug=y%%'' (see also [[user_guide:extend:clients#building_and_debugging|here]]) and make sure to install with ''%%make install Debug=y%%''. When you run the program you need to set ''POLYMAKE_CLIENT_SUFFIX=-d'' either via ''.gdbinit'' or your environment. 
  
  • callable.1549919900.txt.gz
  • Last modified: 2019/02/11 21:18
  • by 127.0.0.1