Conan 1.20 Documentationattributes are evaluated in the workspace context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the MyLib/1.0 binary for any reason (like changes consisting on new functions not used by MyLib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from MyLib/1.0 will definitely require re-building. For this0 码力 | 611 页 | 4.89 MB | 1 年前3
Conan 1.26 Documentationattributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this0 码力 | 669 页 | 5.51 MB | 1 年前3
Conan 1.19 Documentationattributes are evaluated in the workspace context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the MyLib/1.0 binary for any reason (like changes consisting on new functions not used by MyLib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from MyLib/1.0 will definitely require re-building. For this0 码力 | 609 页 | 4.88 MB | 1 年前3
Conan 1.25 Documentationattributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this0 码力 | 655 页 | 5.45 MB | 1 年前3
Conan 1.30 Documentationattributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this0 码力 | 715 页 | 5.39 MB | 1 年前3
Conan 1.31 Documentationattributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this0 码力 | 721 页 | 5.41 MB | 1 年前3
Conan 1.24 Documentationattributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this0 码力 | 647 页 | 5.31 MB | 1 年前3
Conan 1.27 Documentationattributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this0 码力 | 681 页 | 5.55 MB | 1 年前3
Conan 1.29 Documentationattributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this0 码力 | 703 页 | 5.41 MB | 1 年前3
Conan 1.21 Documentationattributes are evaluated in the workspace context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the MyLib/1.0 binary for any reason (like changes consisting on new functions not used by MyLib). The same reasoning would apply if MyOtherLib was only the header. But what new methods to the public headers will have no impact, but changing the implementation of some functions that will be inlined when compiled from MyLib/1.0 will definitely require re-building. For this0 码力 | 621 页 | 4.92 MB | 1 年前3
共 74 条
- 1
- 2
- 3
- 4
- 5
- 6
- 8













