Building 64-bit Packages for Business Function Development

If you are building a package to use in developing 64-bit business functions, you will need to select the Generate NER Headers for Opposite bitness check box in the Package Definition application. When you compile a 64-bit business function in OMW with Busbuild on a 32-bit development client the NER headers (n*.h) for 64-bit will have to be present on the client machine for the compile to be successful. This is done during the client package build prior to building the business functions.

When you define a package in the Package Definition application for building business functions, you must select the 'Generate NER headers for Opposite bitness' check box. This creates the NER headers ( n*.h) for the opposite bitness under include64 or include.

If the package is a 32-bit package and the box is checked, then the headers for NER are generated into the include64 directory of the package.

If the package is a 64-bit package and the box is checked, then the headers for NER are generated into the include directory of the package.

The Generation of these NER headers are displayed under in the buildlog.txt, <deployment server>\<pathcode>\<package name>\work\buildlog.txt.

If you do not select the option to Generate NER headers for Opposite bitness during the package build, the NER headers for the opposite bitness are not present in the include or include64 directory. You will see these errors when compiling the opposite bitness in OMW with Busbuild.