4590ade6ba01e0166c0a851f1/p1_1.jpg) Firebird Generator Guide A guide on how and when to use generators in Firebird Frank Ingermann Version 0.3, 27 June 2020 ## Table of Contents 1. Introduction 3 2.3. Where are generators stored? ..... 3 2.4. What is the maximum value of a generator? ..... 4 2.4.1. Client dialects and generator values ..... 5 2.5. How many generators are available in one 5 2.5.1. Older InterBase and Firebird versions ..... 6 2.6. Generators and transactions ..... 6 3. SQL statements for generators ..... 7 3.1. Statement overview ..... 7 3.1.1. Firebird 2 recommended

373 18.1 Commands ..... 373 18.2 conanfile.txt ..... 451 18.3 conanfile.py ..... 453 18.4 Generators ..... 546 18.5 Profiles ..... 586 18.6 Build helpers ..... 592 18.7 Tools ..... 618 18 install ## Consume packages in build system via generators $ cat conanfile.txt [requires] zlib/1.2.11 [generators] cnake_find_package msbuild make ## I nstall requirements and configuration: [requires] boost/1.72.0 → graph poco/1.9.4 [build_requires] → application 7zip/16.00 [generators] → dependency information, make → settings and options [options] → dependency graph boost:shared=True

327 16.1 Commands ..... 327 16.2 conanfile.txt ..... 399 16.3 conanfile.py ..... 401 16.4 Generators ..... 447 16.5 Profiles ..... 485 16.6 Build helpers ..... 490 16.7 Tools ..... 516 16 'building', 'networking', 'server', 'mobile', 'embedded') generators: cmake exports: None exports_sources: CMakeLists.txt short_paths: False apply_env: True build_policy: project's folder with the following content: Listing 2: conanfile.txt [requires] poco/1.9.4 [generators] (continues on next page) cmake (continued from previous page) In this example we are using CMake

231 14.1 Commands ..... 231 14.2 conanfile.txt ..... 281 14.3 conanfile.py ..... 284 14.4 Generators ..... 317 14.5 Profiles ..... 342 14.6 Build helpers ..... 347 14.7 Tools ..... 369 14 network- and internet-based applications that run on desktop, server, mobile and embedded systems. generators: ('cmake', 'txt') exports: None exports_sources: ('CMakeLists.txt', 'PocoMacros with the following content: Listing 2: conanfile.txt [requires] Poco/1.9.0@pocoproject/stable [generators] cmake In this example we are using CMake to build the project, which is why the cmake generator

239 14.1 Commands ..... 239 14.2 conanfile.txt ..... 290 14.3 conanfile.py ..... 292 14.4 Generators ..... 326 14.5 Profiles ..... 351 14.6 Build helpers ..... 356 14.7 Tools ..... 378 14 network- and internet-based applications that run on desktop, server, mobile and embedded systems. generators: ('cmake', 'txt') exports: None exports_sources: ('CMakeLists.txt', 'PocoMacros with the following content: Listing 2: conanfile.txt [requires] Poco/1.9.0@pocoproject/stable [generators] cmake In this example we are using CMake to build the project, which is why the cmake generator

→network- and internet-based applications that run on desktop, server, →mobile and embedded systems. generators: ('make', 'txt') exports: None exports_sources: ('MakeLists.txt', 'PocoMacros with the following content: Listing 2: conanfile.txt [requires] Poco/1.9.0@pocoproject/stable [generators] cmake In this example we are using CMake to build the project, which is why the cmake generator CMake variables including paths and library names that can be used in our build. Read more about Generators. 6. Next step: We are going to install the required dependencies and generate the information

14 Reference 249 14.1 Commands 249 14.2 conanfile.txt 306 14.3 conanfile.py 308 14.4 Generators 343 14.5 Profiles 369 14.6 Build helpers 374 14.7 Tools 397 14.8 Configuration files 423 network- and internet-based applications that run on desktop, server, mobile and embedded systems. generators: ('cmake', 'txt') exports: None exports_sources: ('CMakeLists.txt', 'PocoMacros with the following content: Listing 2: conanfile.txt [requires] Poco/1.9.0@pocoproject/stable [generators] cmake In this example we are using CMake to build the project, which is why the cmake generator

18 Reference 393 18.1 Commands 393 18.2 conanfile.txt 470 18.3 conanfile.py 473 18.4 Generators 660 18.5 Profiles 702 18.6 Build helpers 709 18.7 Tools 735 18.8 Configuration files 768 information needed to build the current package has to be calculated and written in disk (in the self.generators_folder) by the generate() method. The goal of the generate() method is to prepare the build generating • Write information about the dependencies for the build system. This is done by what we call “generators”, which are tools like CMakeDeps, PkgConfigDeps, MSBuildDeps, XcodeDeps, etc. • Write information

18 Reference 403 18.1 Commands 403 18.2 conanfile.txt 484 18.3 conanfile.py 487 18.4 Generators 678 18.5 Profiles 720 18.6 Build helpers 728 18.7 Tools 754 18.8 Configuration files 788 information needed to build the current package has to be calculated and written in disk (in the self.generators_folder) by the generate() method. The goal of the generate() method is to prepare the build generating • Write information about the dependencies for the build system. This is done by what we call “generators”, which are tools like CMakeDeps, PkgConfigDeps, MSBuildDeps, XcodeDeps, etc. • Write information

18 Reference 405 18.1 Commands 405 18.2 conanfile.txt 486 18.3 conanfile.py 489 18.4 Generators 680 18.5 Profiles 722 18.6 Build helpers 730 18.7 Tools 756 18.8 Configuration files 790 information needed to build the current package has to be calculated and written in disk (in the self.generators_folder) by the generate() method. The goal of the generate() method is to prepare the build generating • Write information about the dependencies for the build system. This is done by what we call “generators”, which are tools like CMakeDeps, PkgConfigDeps, MSBuildDeps, XcodeDeps, etc. • Write information