Chiebot-Mirror
/
meson
mirror of https://github.com/mesonbuild/meson.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
The Meson Build System http://mesonbuild.com/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3950 Commits
76 Branches
171 Tags
74 MiB
Tag: Branch: Tree: efef8f4f38
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'efef8f4f38'
${ noResults }
meson/test cases/osx/2 library versions/meson.build

44 lines
1.4 KiB
Raw Normal View History Unescape

Fix tests for the new library/executable naming scheme Also add new tests for the platform-specific and compiler-specific versioning scheme. A rough summary is: 1. A bug in how run_tests.py:validate_install checked for files has been fixed. Earlier it wasn't checking the install directory properly. 2. Shared libraries are no longer installed in common tests, and the library name/path testing is now done in platform-specific tests. 3. Executables are now always called something?exe in the installed_files.txt file, and the suffix automatically corrected depending on the platform. 4. If a test installs a file called 'no-installed-files', the installed files for that test are not validated. This is required to implement compiler-specific tests for library names/paths such as MSVC vs MinGW 5. The platform-specific file renaming in run_tests.py has been mostly removed since it is broken for shared libraries and isn't needed for static libraries. 6. run_tests.py now reports all missing and extra files. The logic for finding these has been reworked.
9 years ago
project('library versions', 'c')
Add a test to find libfoo.X.dylib via -lfoo Alex Băluț reported that on OS X libfoo.0.dylib cannot be found as -lfoo by the linker, and you must use -lfoo.0 instead. Add a test for this so the CI can catch such problems. The next commit will contain the fix.
8 years ago
some = shared_library('some', 'lib.c',
Fix tests for the new library/executable naming scheme Also add new tests for the platform-specific and compiler-specific versioning scheme. A rough summary is: 1. A bug in how run_tests.py:validate_install checked for files has been fixed. Earlier it wasn't checking the install directory properly. 2. Shared libraries are no longer installed in common tests, and the library name/path testing is now done in platform-specific tests. 3. Executables are now always called something?exe in the installed_files.txt file, and the suffix automatically corrected depending on the platform. 4. If a test installs a file called 'no-installed-files', the installed files for that test are not validated. This is required to implement compiler-specific tests for library names/paths such as MSVC vs MinGW 5. The platform-specific file renaming in run_tests.py has been mostly removed since it is broken for shared libraries and isn't needed for static libraries. 6. run_tests.py now reports all missing and extra files. The logic for finding these has been reworked.
9 years ago
version : '1.2.3',
soversion : '0',
install : true)
Add a test to find libfoo.X.dylib via -lfoo Alex Băluț reported that on OS X libfoo.0.dylib cannot be found as -lfoo by the linker, and you must use -lfoo.0 instead. Add a test for this so the CI can catch such problems. The next commit will contain the fix.
8 years ago
noversion = shared_library('noversion', 'lib.c',
Fix tests for the new library/executable naming scheme Also add new tests for the platform-specific and compiler-specific versioning scheme. A rough summary is: 1. A bug in how run_tests.py:validate_install checked for files has been fixed. Earlier it wasn't checking the install directory properly. 2. Shared libraries are no longer installed in common tests, and the library name/path testing is now done in platform-specific tests. 3. Executables are now always called something?exe in the installed_files.txt file, and the suffix automatically corrected depending on the platform. 4. If a test installs a file called 'no-installed-files', the installed files for that test are not validated. This is required to implement compiler-specific tests for library names/paths such as MSVC vs MinGW 5. The platform-specific file renaming in run_tests.py has been mostly removed since it is broken for shared libraries and isn't needed for static libraries. 6. run_tests.py now reports all missing and extra files. The logic for finding these has been reworked.
9 years ago
install : true)
Add a test to find libfoo.X.dylib via -lfoo Alex Băluț reported that on OS X libfoo.0.dylib cannot be found as -lfoo by the linker, and you must use -lfoo.0 instead. Add a test for this so the CI can catch such problems. The next commit will contain the fix.
8 years ago
onlyversion = shared_library('onlyversion', 'lib.c',
Fix tests for the new library/executable naming scheme Also add new tests for the platform-specific and compiler-specific versioning scheme. A rough summary is: 1. A bug in how run_tests.py:validate_install checked for files has been fixed. Earlier it wasn't checking the install directory properly. 2. Shared libraries are no longer installed in common tests, and the library name/path testing is now done in platform-specific tests. 3. Executables are now always called something?exe in the installed_files.txt file, and the suffix automatically corrected depending on the platform. 4. If a test installs a file called 'no-installed-files', the installed files for that test are not validated. This is required to implement compiler-specific tests for library names/paths such as MSVC vs MinGW 5. The platform-specific file renaming in run_tests.py has been mostly removed since it is broken for shared libraries and isn't needed for static libraries. 6. run_tests.py now reports all missing and extra files. The logic for finding these has been reworked.
9 years ago
version : '1.4.5',
install : true)
Add a test to find libfoo.X.dylib via -lfoo Alex Băluț reported that on OS X libfoo.0.dylib cannot be found as -lfoo by the linker, and you must use -lfoo.0 instead. Add a test for this so the CI can catch such problems. The next commit will contain the fix.
8 years ago
onlysoversion = shared_library('onlysoversion', 'lib.c',
Fix tests for the new library/executable naming scheme Also add new tests for the platform-specific and compiler-specific versioning scheme. A rough summary is: 1. A bug in how run_tests.py:validate_install checked for files has been fixed. Earlier it wasn't checking the install directory properly. 2. Shared libraries are no longer installed in common tests, and the library name/path testing is now done in platform-specific tests. 3. Executables are now always called something?exe in the installed_files.txt file, and the suffix automatically corrected depending on the platform. 4. If a test installs a file called 'no-installed-files', the installed files for that test are not validated. This is required to implement compiler-specific tests for library names/paths such as MSVC vs MinGW 5. The platform-specific file renaming in run_tests.py has been mostly removed since it is broken for shared libraries and isn't needed for static libraries. 6. run_tests.py now reports all missing and extra files. The logic for finding these has been reworked.
9 years ago
# Also test that int soversion is acceptable
soversion : 5,
install : true)
Add a test to find libfoo.X.dylib via -lfoo Alex Băluț reported that on OS X libfoo.0.dylib cannot be found as -lfoo by the linker, and you must use -lfoo.0 instead. Add a test for this so the CI can catch such problems. The next commit will contain the fix.
8 years ago
# Hack to make the executables below depend on the shared libraries above
# without actually adding them as `link_with` dependencies since we want to try
# linking to them with -lfoo linker arguments.
out = custom_target('library-dependency-hack',
input : 'exe.orig.c',
output : 'exe.c',
depends : [some, noversion, onlyversion, onlysoversion],
command : ['cp', '@INPUT@', '@OUTPUT@'])
# Manually test if the linker can find the above libraries
# i.e., whether they were generated with the right naming scheme
tests: Minor fixes to the library-usage tests Actually use the myFunc() symbol from the library, and actually run the built executable on macOS.
8 years ago
test('manually linked 1', executable('manuallink1', out,
link_args : ['-L.', '-lsome']))
Add a test to find libfoo.X.dylib via -lfoo Alex Băluț reported that on OS X libfoo.0.dylib cannot be found as -lfoo by the linker, and you must use -lfoo.0 instead. Add a test for this so the CI can catch such problems. The next commit will contain the fix.
8 years ago
tests: Minor fixes to the library-usage tests Actually use the myFunc() symbol from the library, and actually run the built executable on macOS.
8 years ago
test('manually linked 2', executable('manuallink2', out,
link_args : ['-L.', '-lnoversion']))
Add a test to find libfoo.X.dylib via -lfoo Alex Băluț reported that on OS X libfoo.0.dylib cannot be found as -lfoo by the linker, and you must use -lfoo.0 instead. Add a test for this so the CI can catch such problems. The next commit will contain the fix.
8 years ago
tests: Minor fixes to the library-usage tests Actually use the myFunc() symbol from the library, and actually run the built executable on macOS.
8 years ago
test('manually linked 3', executable('manuallink3', out,
link_args : ['-L.', '-lonlyversion']))
Add a test to find libfoo.X.dylib via -lfoo Alex Băluț reported that on OS X libfoo.0.dylib cannot be found as -lfoo by the linker, and you must use -lfoo.0 instead. Add a test for this so the CI can catch such problems. The next commit will contain the fix.
8 years ago
tests: Minor fixes to the library-usage tests Actually use the myFunc() symbol from the library, and actually run the built executable on macOS.
8 years ago
test('manually linked 4', executable('manuallink4', out,
link_args : ['-L.', '-lonlysoversion']))
Don't generate import library for shared modules Also add a test for this on all platforms.
8 years ago
shared_module('module', 'lib.c', install : true)