Conan 1.56 Documentation• self.runenv_info: For the dependent recipes, environment variables will be present during the runtime. Read more about how to use them in the environment management of Conan 2.0. Remember that if you sh script containing environment variables of the run time environment. The launcher contains the runtime environment information, anything that is necessary for the environment to actually run the compiled path.join(self.cpp.build.bindirs[0], "my_app") # The default env is "conanbuild" but we want the runtime here to locate␣ ˓→the shared library self.run(my_app_path, env="conanrun") Check more details0 码力 | 963 页 | 7.67 MB | 1 年前3
Conan 1.55 Documentation• self.runenv_info: For the dependent recipes, environment variables will be present during the runtime. Read more about how to use them in the environment management of Conan 2.0. Remember that if you sh script containing environment variables of the run time environment. The launcher contains the runtime environment information, anything that is necessary for the environment to actually run the compiled path.join(self.cpp.build.bindirs[0], "my_app") # The default env is "conanbuild" but we want the runtime here to locate␣ ˓→the shared library self.run(my_app_path, env="conanrun") Check more details0 码力 | 963 页 | 7.67 MB | 1 年前3
Conan 1.48 Documentationbecause it can’t find the shared libraries in the path. Remember that shared libraries are used at runtime, so the operating system, which is running the application, must be able to locate them. We could libraries must be located in a folder where they can be found, either by the linker, or by the OS runtime. You can add the libraries’ folders to the path (LD_LIBRARY_PATH environment variable in Linux, building with Visual studio the compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if0 码力 | 913 页 | 7.52 MB | 1 年前3
Conan 1.49 Documentationbecause it can’t find the shared libraries in the path. Remember that shared libraries are used at runtime, so the operating system, which is running the application, must be able to locate them. We could libraries must be located in a folder where they can be found, either by the linker, or by the OS runtime. You can add the libraries’ folders to the path (LD_LIBRARY_PATH environment variable in Linux, building with Visual studio the compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if0 码力 | 915 页 | 7.53 MB | 1 年前3
Conan 1.50 Documentation• self.runenv_info: For the dependant recipes, environment variables will be present during the runtime. Read more about how to use them in the environment management of Conan 2.0. Remember that if you sh script containing environment variables of the run time environment. The launcher contains the runtime environment information, anything that is necessary for the environment to actually run the compiled path.join(self.cpp.build.bindirs[0], "my_app") # The default env is "conanbuild" but we want the runtime here to locate␣ ˓→the shared library self.run(my_app_path, env="conanrun") Check more details0 码力 | 923 页 | 7.55 MB | 1 年前3
Conan 1.53 Documentation• self.runenv_info: For the dependant recipes, environment variables will be present during the runtime. Read more about how to use them in the environment management of Conan 2.0. Remember that if you sh script containing environment variables of the run time environment. The launcher contains the runtime environment information, anything that is necessary for the environment to actually run the compiled path.join(self.cpp.build.bindirs[0], "my_app") # The default env is "conanbuild" but we want the runtime here to locate␣ ˓→the shared library self.run(my_app_path, env="conanrun") Check more details0 码力 | 953 页 | 7.64 MB | 1 年前3
Conan 1.54 Documentation• self.runenv_info: For the dependent recipes, environment variables will be present during the runtime. Read more about how to use them in the environment management of Conan 2.0. Remember that if you sh script containing environment variables of the run time environment. The launcher contains the runtime environment information, anything that is necessary for the environment to actually run the compiled path.join(self.cpp.build.bindirs[0], "my_app") # The default env is "conanbuild" but we want the runtime here to locate␣ ˓→the shared library self.run(my_app_path, env="conanrun") Check more details0 码力 | 953 页 | 7.65 MB | 1 年前3
Conan 1.51 Documentation• self.runenv_info: For the dependant recipes, environment variables will be present during the runtime. Read more about how to use them in the environment management of Conan 2.0. Remember that if you sh script containing environment variables of the run time environment. The launcher contains the runtime environment information, anything that is necessary for the environment to actually run the compiled path.join(self.cpp.build.bindirs[0], "my_app") # The default env is "conanbuild" but we want the runtime here to locate␣ ˓→the shared library self.run(my_app_path, env="conanrun") Check more details0 码力 | 933 页 | 7.58 MB | 1 年前3
Conan 1.52 Documentation• self.runenv_info: For the dependant recipes, environment variables will be present during the runtime. Read more about how to use them in the environment management of Conan 2.0. Remember that if you sh script containing environment variables of the run time environment. The launcher contains the runtime environment information, anything that is necessary for the environment to actually run the compiled path.join(self.cpp.build.bindirs[0], "my_app") # The default env is "conanbuild" but we want the runtime here to locate␣ ˓→the shared library self.run(my_app_path, env="conanrun") Check more details0 码力 | 943 页 | 7.62 MB | 1 年前3
Conan 1.47 Documentationbecause it can’t find the shared libraries in the path. Remember that shared libraries are used at runtime, so the operating system, which is running the application, must be able to locate them. We could libraries must be located in a folder where they can be found, either by the linker, or by the OS runtime. You can add the libraries’ folders to the path (LD_LIBRARY_PATH environment variable in Linux, building with Visual studio the compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if0 码力 | 907 页 | 7.50 MB | 1 年前3
共 74 条
- 1
- 2
- 3
- 4
- 5
- 6
- 8













