no short name command line option of cib

demo/1-simple-class/library/CMakeLists.txt

@@ -36,7 +36,7 @@ foreach(CIBOUTFILE ${CIB_OUTPUT})
 endforeach()
 add_custom_command(
 	OUTPUT ${CIB_OUTPUT}
-	COMMAND ${CIB} -i pub -o exp -b cib -m Demo --apidecor=EXAMPLE_API -c ${CMAKE_CURRENT_SOURCE_DIR}/abi/__zz_cib_Demo-ids.h >${CMAKE_LIBRARY_OUTPUT_DIRECTORY}/dev.null
+	COMMAND ${CIB} --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Demo --apidecor=EXAMPLE_API --cib-ids-file ${CMAKE_CURRENT_SOURCE_DIR}/abi/__zz_cib_Demo-ids.h >${CMAKE_LIBRARY_OUTPUT_DIRECTORY}/dev.null
 	DEPENDS cib ${LIBRARY_PUB_FILES}
 	WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
 )

demo/2-interface-class/library/CMakeLists.txt

@@ -33,7 +33,7 @@ foreach(CIBOUTFILE ${CIB_OUTPUT})
 endforeach()
 add_custom_command(
 	OUTPUT ${CIB_OUTPUT}
-	COMMAND ${CIB} -i pub -o exp -b cib -m Demo --apidecor=EXAMPLE_API -c ${CMAKE_CURRENT_SOURCE_DIR}/abi/__zz_cib_Demo-ids.h >${CMAKE_LIBRARY_OUTPUT_DIRECTORY}/dev.null
+	COMMAND ${CIB} --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Demo --apidecor=EXAMPLE_API --cib-ids-file ${CMAKE_CURRENT_SOURCE_DIR}/abi/__zz_cib_Demo-ids.h >${CMAKE_LIBRARY_OUTPUT_DIRECTORY}/dev.null
 	DEPENDS cib ${LIBRARY_PUB_FILES}
 	WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
 )

demo/3-template-class/library/CMakeLists.txt

@@ -34,7 +34,7 @@ foreach(CIBOUTFILE ${CIB_OUTPUT})
 endforeach()
 add_custom_command(
 	OUTPUT ${CIB_OUTPUT}
-	COMMAND ${CIB} -i pub -o exp -b cib -m Demo --apidecor=EXAMPLE_API -c ${CMAKE_CURRENT_SOURCE_DIR}/abi/__zz_cib_template-class-ids.h >${CMAKE_LIBRARY_OUTPUT_DIRECTORY}/dev.null
+	COMMAND ${CIB} --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Demo --apidecor=EXAMPLE_API --cib-ids-file ${CMAKE_CURRENT_SOURCE_DIR}/abi/__zz_cib_template-class-ids.h >${CMAKE_LIBRARY_OUTPUT_DIRECTORY}/dev.null
 	DEPENDS cib ${LIBRARY_PUB_FILES}
 	WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
 )

examples/0010-simple-class/README.md

@@ -53,7 +53,7 @@ CIB  is expected to be run with public headers that a library wants to publish.
 Assuming `pub/` is the folder that contains public headers that library wants to publish and current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folders `cib/` and `exp/`.

examples/0010-simple-class/README.mdpp

@@ -21,7 +21,7 @@ CIB  is expected to be run with public headers that a library wants to publish.
 Assuming `pub/` is the folder that contains public headers that library wants to publish and current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folders `cib/` and `exp/`.

examples/0020-simple-class-and-bkwd-compatibility/Prologue.cmake

@@ -1,4 +1,4 @@
 include("${example_ROOT}/common.cmake")
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example -c ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --cib-ids-file ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
 set(DEPENDS ${PREV_TEST_NAME}_lib) 

examples/0030-simple-class-and-forwd-compatibility/Prologue.cmake

@@ -1,4 +1,4 @@
 include("${example_ROOT}/common.cmake")
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example -c ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --cib-ids-file ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
 set(DEPENDS ${PREV_TEST_NAME}_lib) 

examples/0040-shared-class-and-object-reuse/Prologue.cmake

@@ -6,5 +6,5 @@ set(PUB_FILE_BASE_NAMES
     B
 )
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example -c ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --cib-ids-file ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
 set(DEPENDS ${PREV_TEST_NAME}_lib) 

examples/0050-virtual-function/Prologue.cmake

@@ -1,2 +1,2 @@
-set(CIBCMD ${CIB} -i pub -o exp -b cib -m Example)
+set(CIBCMD ${CIB} --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example)
 

examples/0050-virtual-function/README.md

@@ -33,7 +33,7 @@ Let's now run CIB:
 **Running cib**
 
 ```sh
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 Below is what client of library can expect. It is trivial and there is no surprise but it is being done in **ABI compatible and stable** way.

examples/0050-virtual-function/README.mdpp

@@ -11,7 +11,7 @@ Let's now run CIB:
 **Running cib**
 
 ```sh
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 Below is what client of library can expect. It is trivial and there is no surprise but it is being done in **ABI compatible and stable** way.

examples/0060-virtual-function-and-bkwd-compatibility/Prologue.cmake

@@ -1,4 +1,4 @@
 include("${example_ROOT}/common.cmake")
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example -c ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --cib-ids-file ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
 set(DEPENDS ${PREV_TEST_NAME}_lib) 

examples/0060-virtual-function-and-bkwd-compatibility/README.md

@@ -118,7 +118,7 @@ As it can be seen that the new method caused a new entry in MethodTable and that
 To make CIB ensure ABI stability we needed to run cib with additional parameter and supply ID file of previous example:
 
 ```sh
-cib -i pub -o exp -b cib -m Example -c ../0050-virtual-function/cib/__zz_cib_Example-ids.h
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example -c ../0050-virtual-function/cib/__zz_cib_Example-ids.h
 ```
 
 This makes cib understand that we want ABI stability with previous example and CIB generates glue code accordingly.

examples/0060-virtual-function-and-bkwd-compatibility/README.mdpp

@@ -25,7 +25,7 @@ As it can be seen that the new method caused a new entry in MethodTable and that
 To make CIB ensure ABI stability we needed to run cib with additional parameter and supply ID file of previous example:
 
 ```sh
-cib -i pub -o exp -b cib -m Example -c ../0050-virtual-function/cib/__zz_cib_Example-ids.h
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example -c ../0050-virtual-function/cib/__zz_cib_Example-ids.h
 ```
 
 This makes cib understand that we want ABI stability with previous example and CIB generates glue code accordingly.

examples/0070-virtual-function-and-forwd-compatibility/Prologue.cmake

@@ -1,4 +1,4 @@
 include("${example_ROOT}/common.cmake")
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example -c ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --cib-ids-file ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
 set(DEPENDS ${PREV_TEST_NAME}_lib) 

examples/0070-virtual-function-and-forwd-compatibility/README.md

@@ -84,7 +84,7 @@ Either don't call new functions if client's backward compatibility is desired or
 To make CIB ensure ABI stability we need to run cib with additional parameter to supply ID file of previous version of library:
 
 ```sh
-cib -i pub -o exp -b cib -m Example -c ../0050-virtual-function/cib/__zz_cib_Example-ids.h
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example -c ../0050-virtual-function/cib/__zz_cib_Example-ids.h
 ```
 
 This makes cib understand that we want ABI stability with binaries of `0050-virtual-function` example and CIB generates glue code accordingly.

examples/0070-virtual-function-and-forwd-compatibility/README.mdpp

@@ -18,7 +18,7 @@ Either don't call new functions if client's backward compatibility is desired or
 To make CIB ensure ABI stability we need to run cib with additional parameter to supply ID file of previous version of library:
 
 ```sh
-cib -i pub -o exp -b cib -m Example -c ../0050-virtual-function/cib/__zz_cib_Example-ids.h
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example -c ../0050-virtual-function/cib/__zz_cib_Example-ids.h
 ```
 
 This makes cib understand that we want ABI stability with binaries of `0050-virtual-function` example and CIB generates glue code accordingly.

examples/0090-interface-class-and-bkwd-compatibility/Prologue.cmake

@@ -1,4 +1,4 @@
 include("${example_ROOT}/common.cmake")
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example -c ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --cib-ids-file ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
 set(DEPENDS ${PREV_TEST_NAME}_lib) 

examples/0090-interface-class-and-bkwd-compatibility/README.md

@@ -165,7 +165,7 @@ As it can be seen that the new method caused a new entry in MethodTable and that
 To make CIB ensures ABI stability we needed to run cib with additional parameter and supply ID file of previous example:
 
 ```sh
-cib -i pub -o exp -b cib -m Example -c ../0080-interface-class/cib/__zz_cib_Example-ids.h
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example -c ../0080-interface-class/cib/__zz_cib_Example-ids.h
 ```
 
 This makes cib understand that we want ABI stability with previous example and CIB generates glue code accordingly.

examples/0090-interface-class-and-bkwd-compatibility/README.mdpp

@@ -28,7 +28,7 @@ As it can be seen that the new method caused a new entry in MethodTable and that
 To make CIB ensures ABI stability we needed to run cib with additional parameter and supply ID file of previous example:
 
 ```sh
-cib -i pub -o exp -b cib -m Example -c ../0080-interface-class/cib/__zz_cib_Example-ids.h
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example -c ../0080-interface-class/cib/__zz_cib_Example-ids.h
 ```
 
 This makes cib understand that we want ABI stability with previous example and CIB generates glue code accordingly.

examples/0100-interface-class-and-forwd-compatibility/Prologue.cmake

@@ -1,4 +1,4 @@
 include("${example_ROOT}/common.cmake")
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example -c ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --cib-ids-file ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
 set(DEPENDS ${PREV_TEST_NAME}_lib) 

examples/0100-interface-class-and-forwd-compatibility/README.md

@@ -100,7 +100,7 @@ There isn't much to talk about in this example, just that client is careful in i
 To make CIB ensures ABI stability we needed to run cib with additional parameter and supply ID file of previous example:
 
 ```sh
-cib -i pub -o exp -b cib -m Example -c ../0080-interface-class/cib/__zz_cib_Example-ids.h
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example -c ../0080-interface-class/cib/__zz_cib_Example-ids.h
 ```
 
 This makes cib understand that we want ABI stability with previous example and CIB generates glue code accordingly.

examples/0100-interface-class-and-forwd-compatibility/README.mdpp

@@ -20,7 +20,7 @@ There isn't much to talk about in this example, just that client is careful in i
 To make CIB ensures ABI stability we needed to run cib with additional parameter and supply ID file of previous example:
 
 ```sh
-cib -i pub -o exp -b cib -m Example -c ../0080-interface-class/cib/__zz_cib_Example-ids.h
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example -c ../0080-interface-class/cib/__zz_cib_Example-ids.h
 ```
 
 This makes cib understand that we want ABI stability with previous example and CIB generates glue code accordingly.

examples/0200-lib-managed-proxies/Prologue.cmake

@@ -1 +1 @@
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example)

examples/0300-unique-ptr/Prologue.cmake

@@ -1 +1 @@
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example)

examples/0310-intrusive-ptr/Prologue.cmake

@@ -8,4 +8,4 @@ list(APPEND EXP_SOURCES
     ${example_ROOT}/exp/SkRefCnt.cpp
 )
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example)

examples/0400-stl-template-classes/Prologue.cmake

@@ -1,4 +1,4 @@
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example)
 
 list(APPEND EXP_SOURCES
 	${example_ROOT}/exp/C.cpp

examples/0410-std-function/Prologue.cmake

@@ -1 +1 @@
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example)

examples/0500-layout-sharing-proxy-classes/Prologue.cmake

@@ -1,2 +1,2 @@
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example --value-class CPoint --value-class Dummy)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --value-class CPoint --value-class Dummy)
 

examples/0620-function-overloading/README.md

@@ -55,7 +55,7 @@ Assuming `pub/` is the folder that contains public headers that library wants to
 Assuming current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folder cib/ and exp/.

examples/0620-function-overloading/README.mdpp

@@ -23,7 +23,7 @@ Assuming `pub/` is the folder that contains public headers that library wants to
 Assuming current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folder cib/ and exp/.

examples/0630-operator-overloading/README.md

@@ -55,7 +55,7 @@ Assuming `pub/` is the folder that contains public headers that library wants to
 Assuming current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folder cib/ and exp/.

examples/0630-operator-overloading/README.mdpp

@@ -23,7 +23,7 @@ Assuming `pub/` is the folder that contains public headers that library wants to
 Assuming current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folder cib/ and exp/.

examples/0640-protected-methods/README.md

@@ -55,7 +55,7 @@ Assuming `pub/` is the folder that contains public headers that library wants to
 Assuming current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folder cib/ and exp/.

examples/0640-protected-methods/README.mdpp

@@ -23,7 +23,7 @@ Assuming `pub/` is the folder that contains public headers that library wants to
 Assuming current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folder cib/ and exp/.

examples/0710-exceptions/Prologue.cmake

@@ -1,4 +1,4 @@
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example --exception-class=CustomBaseException)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --exception-class=CustomBaseException)
 
 list(APPEND EXP_SOURCES
   ${example_ROOT}/exp/__zz_cib_internal/__zz_cib_Example-exception-throw-on-error.cpp

examples/0710-exceptions/README.md

@@ -53,7 +53,7 @@ CIB  is expected to be run with public headers that a library wants to publish.
 Assuming `pub/` is the folder that contains public headers that library wants to publish and current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folders `cib/` and `exp/`.

examples/0710-exceptions/README.mdpp

@@ -21,7 +21,7 @@ CIB  is expected to be run with public headers that a library wants to publish.
 Assuming `pub/` is the folder that contains public headers that library wants to publish and current working directory is `examples/0010-simple-class/` we can run CIB as shown below:
 
 ```shell
-cib -i pub/ -o exp/ -b cib/ -m Example
+cib --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example
 ```
 
 After above command we will see quite a good number of files created in folders `cib/` and `exp/`.

examples/0800-inheritance-change-and-bkwd-compatibility/Prologue.cmake

@@ -1,4 +1,4 @@
 include("${example_ROOT}/common.cmake")
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example -c ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --cib-ids-file ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
 set(DEPENDS ${PREV_TEST_NAME}_lib) 

examples/0810-inheritance-type-and-bkwd-compatibility/Prologue.cmake

@@ -1,4 +1,4 @@
 include("${example_ROOT}/common.cmake")
 
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example -c ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --cib-ids-file ${example_ROOT}/../${PREV_TEST_NAME}/cib/__zz_cib_Example-ids.h)
 set(DEPENDS ${PREV_TEST_NAME}_lib) 

examples/0900-force-make-interface-class/Prologue.cmake

@@ -1 +1 @@
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example --interface-class=Interface)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --interface-class=Interface)

examples/0910-interface-class-with-implementation/Prologue.cmake

@@ -1 +1 @@
-set(CIBCMD $<TARGET_FILE:cib> -i pub -o exp -b cib -m Example --interface-class=Interface)
+set(CIBCMD $<TARGET_FILE:cib> --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example --interface-class=Interface)

examples/common.cmake

@@ -16,7 +16,7 @@ set(LIB_GLUE_SRCS
 )
 set(PUB_FILES "")
 set(EXP_SOURCES "")
-set(CIBCMD ${CIB} -i pub -o exp -b cib -m Example)
+set(CIBCMD ${CIB} --input-folder pub/ --output-folder exp/ --bind-folder cib/ --module Example)
 set(DEPENDS cib ${example}GlueCode)
 set(EXAMPLES_BIN_DIR ${CMAKE_BINARY_DIR}/examples)
 set(TEST_CMD ${EXAMPLES_BIN_DIR}/${CLIENTNAME})