Commit faafd676 authored by Joerg Zelenka's avatar Joerg Zelenka

[TASK] Consistency cleanup in build documentation

Use "openPOWERLINK_dir" in build documentation when
referencing to repository root directory.

Change-Id: I50e135aa8965409d4e3624ad33c60f31cac01f97
parent 646497b4
...@@ -7,7 +7,7 @@ Building openPOWERLINK Demo Applications {#page_build_demos} ...@@ -7,7 +7,7 @@ Building openPOWERLINK Demo Applications {#page_build_demos}
The following section describes how the delivered demo applications can be The following section describes how the delivered demo applications can be
built. The demo applications are located in the directory `apps`. The default built. The demo applications are located in the directory `apps`. The default
binary installation path is: `<openPOWERLINK_DIR>/bin/<platform>/<ARCH>` binary installation path is: `<openPOWERLINK_dir>/bin/<platform>/<ARCH>`
__NOTE:__ In order to be able to build an application, the Debug or the __NOTE:__ In order to be able to build an application, the Debug or the
Release library versions must be available, depending on your CMAKE_BUILD_TYPE. Release library versions must be available, depending on your CMAKE_BUILD_TYPE.
...@@ -170,7 +170,7 @@ Follow the steps below to cross compile your demo application for Altera Cyclone ...@@ -170,7 +170,7 @@ Follow the steps below to cross compile your demo application for Altera Cyclone
- **CFG_HW_LIB_DIR** - **CFG_HW_LIB_DIR**
Path to the hardware platform install directory your application should refer to. Path to the hardware platform install directory your application should refer to.
(e.g: `<openPOWERLINK_DIR>/hardware/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`) (e.g: `<openPOWERLINK_dir>/hardware/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`)
- **CFG_BUILD_KERNEL_STACK** - **CFG_BUILD_KERNEL_STACK**
...@@ -194,7 +194,7 @@ Follow the steps below to cross compile your demo application for Altera Cyclone ...@@ -194,7 +194,7 @@ Follow the steps below to cross compile your demo application for Altera Cyclone
- **CFG_HW_LIB_DIR** - **CFG_HW_LIB_DIR**
Path to the hardware platform install directory that the application should refer to. Path to the hardware platform install directory that the application should refer to.
(e.g: `<openPOWERLINK_DIR>/hardware/lib/generic/alterac5arm/<BOARD_NAME>/<DEMO_NAME>`) (e.g: `<openPOWERLINK_dir>/hardware/lib/generic/alterac5arm/<BOARD_NAME>/<DEMO_NAME>`)
- **CFG_BUILD_KERNEL_STACK** - **CFG_BUILD_KERNEL_STACK**
...@@ -211,7 +211,7 @@ Follow the steps below to cross compile your demo application for Altera Cyclone ...@@ -211,7 +211,7 @@ Follow the steps below to cross compile your demo application for Altera Cyclone
- **CFG_DRV_BLD_PATH** - **CFG_DRV_BLD_PATH**
Path to the driver daemon build location that the application should refer to. Path to the driver daemon build location that the application should refer to.
(e.g: `<openPOWERLINK_DIR>/drivers/altera-nios2/drv_daemon/build`) (e.g: `<openPOWERLINK_dir>/drivers/altera-nios2/drv_daemon/build`)
- **CFG_DRV_BIN** - **CFG_DRV_BIN**
......
...@@ -55,7 +55,7 @@ To build the kernel PCIe interface driver: ...@@ -55,7 +55,7 @@ To build the kernel PCIe interface driver:
> make > make
> make install > make install
The default driver installation path is: `<openPOWERLINK_DIR>/bin/linux/<ARCH>/oplkdrv_kernelmodule_pcie` The default driver installation path is: `<openPOWERLINK_dir>/bin/linux/<ARCH>/oplkdrv_kernelmodule_pcie`
## Building a Linux Kernel Interface Driver for Zynq Hybrid Design {#sect_build_drivers_build_linux_zynq} ## Building a Linux Kernel Interface Driver for Zynq Hybrid Design {#sect_build_drivers_build_linux_zynq}
...@@ -70,7 +70,7 @@ To build the kernel interface driver for Zynq hybrid: ...@@ -70,7 +70,7 @@ To build the kernel interface driver for Zynq hybrid:
> make > make
> make install > make install
The default driver installation path is: `<openPOWERLINK_DIR>/bin/linux/<ARCH>/oplkdrv_kernelmodule_zynq` The default driver installation path is: `<openPOWERLINK_dir>/bin/linux/<ARCH>/oplkdrv_kernelmodule_zynq`
## Building a Windows NDIS driver {#sect_build_drivers_build_windows_ndis} ## Building a Windows NDIS driver {#sect_build_drivers_build_windows_ndis}
...@@ -92,20 +92,20 @@ Open a Visual Studio command line and enter the following commands: ...@@ -92,20 +92,20 @@ Open a Visual Studio command line and enter the following commands:
* Build driver for Windows 7 (64 bit) in debug mode * Build driver for Windows 7 (64 bit) in debug mode
> cd <openPOWERLINK_directory>\drivers\windows\drv_ndis_[pcie;intermediate]\build > cd <openPOWERLINK_dir>\drivers\windows\drv_ndis_[pcie;intermediate]\build
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug .. > cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug ..
> msbuild /t:build /p:Platform=x64 /p:Configuration="Win7 Debug" > msbuild /t:build /p:Platform=x64 /p:Configuration="Win7 Debug"
* Build driver for Windows 7 (64 bit) in release mode * Build driver for Windows 7 (64 bit) in release mode
> cd <openPOWERLINK_directory>\drivers\windows\drv_ndis_[pcie;intermediate]\build > cd <openPOWERLINK_dir>\drivers\windows\drv_ndis_[pcie;intermediate]\build
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release .. > cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release ..
> msbuild /t:build /p:Platform=x64 /p:Configuration="Win7 Release" > msbuild /t:build /p:Platform=x64 /p:Configuration="Win7 Release"
`Platform` and `Configuration` parameters can be modified to compile the driver for `Platform` and `Configuration` parameters can be modified to compile the driver for
a different platform and Windows version. a different platform and Windows version.
The default driver installation path is: `<openPOWERLINK_DIR>\bin\windows\<ARCH>\drv_ndis_[pcie;intermediate]_package` The default driver installation path is: `<openPOWERLINK_dir>\bin\windows\<ARCH>\drv_ndis_[pcie;intermediate]_package`
## Building a PCP daemon for Microblaze (ISE) {#sect_build_drivers_build_daemon_microblazeise} ## Building a PCP daemon for Microblaze (ISE) {#sect_build_drivers_build_daemon_microblazeise}
...@@ -216,7 +216,7 @@ Following options are available for a PCP daemon of a dual processor design: ...@@ -216,7 +216,7 @@ Following options are available for a PCP daemon of a dual processor design:
- **CFG_HW_LIB_DIR** - **CFG_HW_LIB_DIR**
Path to the hardware platform installation directory your daemon should refer to. Path to the hardware platform installation directory your daemon should refer to.
(e.g: `<openPOWERLINK_DIR>/hardware/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`) (e.g: `<openPOWERLINK_dir>/hardware/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`)
- **CFG_BUILD_KERNEL_STACK** - **CFG_BUILD_KERNEL_STACK**
......
...@@ -28,7 +28,7 @@ hardware-dependent drivers. ...@@ -28,7 +28,7 @@ hardware-dependent drivers.
-# Initialize the hardware platform build system -# Initialize the hardware platform build system
> cd openPOWERLINK/hardware/build/xilinx-microblaze > cd <openPOWERLINK_dir>/hardware/build/xilinx-microblaze
> cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-ise-microblaze-gnu.cmake ../.. > cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-ise-microblaze-gnu.cmake ../..
After this command CMake will search for available hardware platforms and After this command CMake will search for available hardware platforms and
...@@ -76,12 +76,12 @@ hardware-dependent drivers. ...@@ -76,12 +76,12 @@ hardware-dependent drivers.
* On a Windows host platform * On a Windows host platform
> cd openPOWERLINK/hardware/build/xilinx-microblaze > cd <openPOWERLINK_dir>/hardware/build/xilinx-microblaze
> cmake -GUnix\ Makefiles -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. > cmake -GUnix\ Makefiles -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../..
* On a Linux host platform * On a Linux host platform
> cd openPOWERLINK/hardware/build/xilinx-microblaze > cd <openPOWERLINK_dir>/hardware/build/xilinx-microblaze
> cmake -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. > cmake -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../..
After this command CMake will search for available hardware platforms and After this command CMake will search for available hardware platforms and
...@@ -116,7 +116,7 @@ For Cyclone V SoC ARM bsp and preloader generation, execute the following steps ...@@ -116,7 +116,7 @@ For Cyclone V SoC ARM bsp and preloader generation, execute the following steps
-# Initialize the hardware platform build system -# Initialize the hardware platform build system
> cd openPOWERLINK/hardware/build/altera-c5socarm > cd <openPOWERLINK_dir>/hardware/build/altera-c5socarm
> cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-altera-c5socarm-eabi-gnu.cmake ../.. > cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-altera-c5socarm-eabi-gnu.cmake ../..
After this command CMake will search for available hardware platforms and After this command CMake will search for available hardware platforms and
......
...@@ -23,19 +23,19 @@ generates Makefiles by default. ...@@ -23,19 +23,19 @@ generates Makefiles by default.
* Create debug libraries * Create debug libraries
> cd openPOWERLINK/stack/build/linux > cd <openPOWERLINK_dir>/stack/build/linux
> cmake -DCMAKE_BUILD_TYPE=Debug ../.. > cmake -DCMAKE_BUILD_TYPE=Debug ../..
> make > make
> make install > make install
* Create release libraries * Create release libraries
> cd openPOWERLINK/stack/build/linux > cd <openPOWERLINK_dir>/stack/build/linux
> cmake -DCMAKE_BUILD_TYPE=Release ../.. > cmake -DCMAKE_BUILD_TYPE=Release ../..
> make > make
> make install > make install
The default library installation path is: `<openPOWERLINK_DIR>/lib/linux/<ARCH>` The default library installation path is: `<openPOWERLINK_dir>/lib/linux/<ARCH>`
## Windows {#sect_build_stack_build_windows} ## Windows {#sect_build_stack_build_windows}
...@@ -45,19 +45,19 @@ Open a Visual Studio command line and enter the following commands: ...@@ -45,19 +45,19 @@ Open a Visual Studio command line and enter the following commands:
* Create debug libraries * Create debug libraries
> cd <openPOWERLINK_directory>\stack\build\windows > cd <openPOWERLINK_dir>\stack\build\windows
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug ..\.. > cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug ..\..
> nmake > nmake
> nmake install > nmake install
* Create release libraries * Create release libraries
> cd <openPOWERLINK_directory>\stack\build\windows > cd <openPOWERLINK_dir>\stack\build\windows
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release ..\.. > cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release ..\..
> nmake > nmake
> nmake install > nmake install
The default library installation path is: `<openPOWERLINK_DIR>\lib\windows\<ARCH>` The default library installation path is: `<openPOWERLINK_dir>\lib\windows\<ARCH>`
__NOTE:__ You can also generate a Visual Studio Solution and compile the __NOTE:__ You can also generate a Visual Studio Solution and compile the
libraries in Visual Studio. Please refer to the CMAKE documentation for libraries in Visual Studio. Please refer to the CMAKE documentation for
...@@ -76,7 +76,7 @@ Follow the steps below to build the stack library on your host platform: ...@@ -76,7 +76,7 @@ Follow the steps below to build the stack library on your host platform:
* Create debug libraries * Create debug libraries
> cd <openPOWERLINK_directory>\stack\build\xilinx-microblaze > cd <openPOWERLINK_dir>\stack\build\xilinx-microblaze
> cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-ise-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Debug -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB] > cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-ise-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Debug -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB]
> make all > make all
> make install > make install
...@@ -88,7 +88,7 @@ Follow the steps below to build the stack library on your host platform: ...@@ -88,7 +88,7 @@ Follow the steps below to build the stack library on your host platform:
* Create release libraries * Create release libraries
> cd <openPOWERLINK_directory>\stack\build\xilinx-microblaze > cd <openPOWERLINK_dir>\stack\build\xilinx-microblaze
> cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-ise-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Release -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB] > cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-ise-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Release -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB]
> make all > make all
> make install > make install
...@@ -99,7 +99,7 @@ Follow the steps below to build the stack library on your host platform: ...@@ -99,7 +99,7 @@ Follow the steps below to build the stack library on your host platform:
Refer to \ref sect_build_stack_options_noos_microblaze for details! Refer to \ref sect_build_stack_options_noos_microblaze for details!
The default library installation path is: The default library installation path is:
`<openPOWERLINK_DIR>/stack/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>` `<openPOWERLINK_dir>/stack/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`
### Xilinx Microblaze (Vivado) {#sect_build_stack_build_microblaze} ### Xilinx Microblaze (Vivado) {#sect_build_stack_build_microblaze}
...@@ -121,14 +121,14 @@ Follow the steps below to build the stack library on your host platform: ...@@ -121,14 +121,14 @@ Follow the steps below to build the stack library on your host platform:
* On a Windows host platform * On a Windows host platform
> cd <openPOWERLINK_directory>\stack\build\xilinx-microblaze > cd <openPOWERLINK_dir>\stack\build\xilinx-microblaze
> cmake -GUnix\ Makefiles -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Debug -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB] > cmake -GUnix\ Makefiles -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Debug -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB]
> make all > make all
> make install > make install
* On a Linux host platform * On a Linux host platform
> cd <openPOWERLINK_directory>\stack\build\xilinx-microblaze > cd <openPOWERLINK_dir>\stack\build\xilinx-microblaze
> cmake -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Debug -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB] > cmake -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Debug -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB]
> make all > make all
> make install > make install
...@@ -142,14 +142,14 @@ Follow the steps below to build the stack library on your host platform: ...@@ -142,14 +142,14 @@ Follow the steps below to build the stack library on your host platform:
* On a Windows host platform * On a Windows host platform
> cd <openPOWERLINK_directory>\stack\build\xilinx-microblaze > cd <openPOWERLINK_dir>\stack\build\xilinx-microblaze
> cmake -GUnix\ Makefiles -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Release -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB] > cmake -GUnix\ Makefiles -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Release -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB]
> make all > make all
> make install > make install
* On a Linux host platform * On a Linux host platform
> cd <openPOWERLINK_directory>\stack\build\xilinx-microblaze > cd <openPOWERLINK_dir>\stack\build\xilinx-microblaze
> cmake -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Release -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB] > cmake -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-xilinx-microblaze-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Release -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB]
> make all > make all
> make install > make install
...@@ -160,7 +160,7 @@ Follow the steps below to build the stack library on your host platform: ...@@ -160,7 +160,7 @@ Follow the steps below to build the stack library on your host platform:
Refer to \ref sect_build_stack_options_noos_microblaze for details! Refer to \ref sect_build_stack_options_noos_microblaze for details!
The default library installation path is: The default library installation path is:
`<openPOWERLINK_DIR>/stack/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>` `<openPOWERLINK_dir>/stack/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`
### Altera Cyclone V SoC ARM {#sect_build_stack_build_c5socarm-altera} ### Altera Cyclone V SoC ARM {#sect_build_stack_build_c5socarm-altera}
...@@ -170,7 +170,7 @@ Follow the steps below to build the stack library on your host platform: ...@@ -170,7 +170,7 @@ Follow the steps below to build the stack library on your host platform:
* Create debug libraries * Create debug libraries
> cd <openPOWERLINK_directory>\stack\build\altera-c5socarm > cd <openPOWERLINK_dir>\stack\build\altera-c5socarm
> cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-altera-c5socarm-eabi-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Debug -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB] > cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../../cmake/toolchain-altera-c5socarm-eabi-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Debug -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB]
> make all > make all
> make install > make install
...@@ -182,7 +182,7 @@ Follow the steps below to build the stack library on your host platform: ...@@ -182,7 +182,7 @@ Follow the steps below to build the stack library on your host platform:
* Create release libraries * Create release libraries
> cd <openPOWERLINK_directory>\stack\build\altera-c5socarm > cd <openPOWERLINK_dir>\stack\build\altera-c5socarm
> cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../toolchain-altera-c5socarm-eabi-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Release -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB] > cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=../../toolchain-altera-c5socarm-eabi-gnu.cmake ../.. -DCMAKE_BUILD_TYPE=Release -DCFG_COMPILE_LIB_[LIB_NAME]=ON -DCFG_COMPILE_LIB_[LIB_NAME]_LIB_DIR=[PATH_TO_HW_LIB]
> make all > make all
> make install > make install
...@@ -193,7 +193,7 @@ Follow the steps below to build the stack library on your host platform: ...@@ -193,7 +193,7 @@ Follow the steps below to build the stack library on your host platform:
Refer to \ref sect_build_stack_options_noos_c5socarm for details! Refer to \ref sect_build_stack_options_noos_c5socarm for details!
The default library installation path is: The default library installation path is:
`<openPOWERLINK_DIR>/stack/lib/generic/alterac5arm/<BOARD_NAME>/<DEMO_NAME>` `<openPOWERLINK_dir>/stack/lib/generic/alterac5arm/<BOARD_NAME>/<DEMO_NAME>`
# Configuration Options {#sect_build_stack_options} # Configuration Options {#sect_build_stack_options}
...@@ -211,7 +211,7 @@ the configuration options on the command line (-DCFG_XXX=XXX) or ...@@ -211,7 +211,7 @@ the configuration options on the command line (-DCFG_XXX=XXX) or
Specifies the installation directory where your files will be installed. Specifies the installation directory where your files will be installed.
Default directory is: `<openPOWERLINK_DIR>/lib/${SYSTEM_DIR_NAME}/${CMAKE_SYSTEM_PROCESSOR}` Default directory is: `<openPOWERLINK_dir>/lib/${SYSTEM_DIR_NAME}/${CMAKE_SYSTEM_PROCESSOR}`
- **CMAKE_BUILD_TYPE** - **CMAKE_BUILD_TYPE**
...@@ -375,7 +375,7 @@ the configuration options on the command line (-DCFG_XXX=XXX) or ...@@ -375,7 +375,7 @@ the configuration options on the command line (-DCFG_XXX=XXX) or
Specify the path to the hardware platform the CN library should refer to. Specify the path to the hardware platform the CN library should refer to.
The path to the hardware platform should point to the export folder of the hardware The path to the hardware platform should point to the export folder of the hardware
project. (e.g: `<openPOWERLINK_DIR>/hardware/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`) project. (e.g: `<openPOWERLINK_dir>/hardware/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`)
- **CFG_COMPILE_LIB_MNDRV_HOSTIF** - **CFG_COMPILE_LIB_MNDRV_HOSTIF**
...@@ -390,7 +390,7 @@ the configuration options on the command line (-DCFG_XXX=XXX) or ...@@ -390,7 +390,7 @@ the configuration options on the command line (-DCFG_XXX=XXX) or
Specify the path to the hardware platform the driver library should refer to. Specify the path to the hardware platform the driver library should refer to.
The path to the hardware platform should point to the export folder of the hardware The path to the hardware platform should point to the export folder of the hardware
project. (e.g: `<openPOWERLINK_DIR>/hardware/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`) project. (e.g: `<openPOWERLINK_dir>/hardware/lib/generic/microblaze/<BOARD_NAME>/<DEMO_NAME>`)
### Altera Cyclone V SoC ARM Configuration Options {#sect_build_stack_options_noos_c5socarm} ### Altera Cyclone V SoC ARM Configuration Options {#sect_build_stack_options_noos_c5socarm}
...@@ -409,4 +409,4 @@ the configuration options on the command line (-DCFG_XXX=XXX) or ...@@ -409,4 +409,4 @@ the configuration options on the command line (-DCFG_XXX=XXX) or
Specifies the path to the hardware platform the application library should refer to. Specifies the path to the hardware platform the application library should refer to.
The path to the hardware platform should point to the export folder of the hardware The path to the hardware platform should point to the export folder of the hardware
project. (e.g: `<openPOWERLINK_DIR>/hardware/lib/generic/alterac5arm/<BOARD_NAME>/<DEMO_NAME>`) project. (e.g: `<openPOWERLINK_dir>/hardware/lib/generic/alterac5arm/<BOARD_NAME>/<DEMO_NAME>`)
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment