Makefiles

The emulation mode makefile syntax used in Release 5 (or higher) is different than in previous releases. See the makefiles in the samples directory for the new syntax. You must change your existing makefiles to conform to the new syntax.

If your existing makefiles include cfgbuild.mak, you should be able to recompile existing non-emulation code without making any changes, other than changing the path separators, as described below. If you only used cfgbuild.mak as an example, changes will be required in your makefiles for the new toolchain. See the makefiles in the samples directory, and the cfgbuild.mak file.

Path Separators

When building for SafeNet ProtectServer PCIe HSM on Linux hosts, all path separators in your makefiles must use forward slashes ( / ). Windows-style backslashes ( \ ) will not work.

NOTE Change all backslashes ( \ ) to forward slashes ( / ) in your makefiles.

The cfgbuild.mak File

For both FMs and HOST applications, cfgbuild.mak is now a supported file and not a simply an example. The cfgbuild.mak file has been moved to $(FMDIR)/ from $(FMDIR)/samples. A wrapper is provided in $(FMDIR)/samples for compatibility.

The default libraries provided by the FM SDK are now automatically included by cfgbuild.mak and should not be specified within the FM's makefile directly.

NOTE For best practice, include cfgbuild.mak in all of your makefiles to set up the compiler, link flags, and link the FM toolchain.