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.
3445 Commits
76 Branches
171 Tags
74 MiB
Tag: Branch: Tree: 98b1ce1cd9
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '98b1ce1cd9'
${ noResults }
meson/test cases/windows/7 mingw dll versioning/meson.build

54 lines
1.6 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('mingw dll versioning', 'c')
cc = meson.get_compiler('c')
tests: Use the new test skipping facility everywhere
8 years ago
if cc.get_id() == 'msvc'
error('MESON_SKIP_TEST: test is only for MinGW')
endif
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
# Test that MinGW/GCC creates correctly-named dll files and dll.a files,
# and also installs them in the right place
Add manual-linking tests to Linux and Windows In this test, we try to manually link against the generated library to create an executable and then run it to verify that it works. Also test for all possible library versioning in the versioning tests on Windows. Even though they yield the same dll naming, we should still test it.
8 years ago
some = shared_library('some', 'lib.c',
tests: Use the new test skipping facility everywhere
8 years ago
version : '1.2.3',
soversion : '0',
install : true)
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
Add manual-linking tests to Linux and Windows In this test, we try to manually link against the generated library to create an executable and then run it to verify that it works. Also test for all possible library versioning in the versioning tests on Windows. Even though they yield the same dll naming, we should still test it.
8 years ago
noversion = shared_library('noversion', 'lib.c',
tests: Use the new test skipping facility everywhere
8 years ago
install : true)
Add manual-linking tests to Linux and Windows In this test, we try to manually link against the generated library to create an executable and then run it to verify that it works. Also test for all possible library versioning in the versioning tests on Windows. Even though they yield the same dll naming, we should still test it.
8 years ago
onlyversion = shared_library('onlyversion', 'lib.c',
version : '1.4.5',
install : true)
onlysoversion = shared_library('onlysoversion', 'lib.c',
# Also test that int soversion is acceptable
soversion : 5,
install : true)
# 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
test('manually linked 1', executable('manuallink1', out,
link_args : ['-L.', '-lsome']))
test('manually linked 2', executable('manuallink2', out,
link_args : ['-L.', '-lnoversion']))
test('manually linked 3', executable('manuallink3', out,
link_args : ['-L.', '-lonlyversion']))
test('manually linked 4', executable('manuallink4', out,
link_args : ['-L.', '-lonlysoversion']))
Fix custom directory installation of import library When install_dir was set for a shared_library, the import library would not be installed at all, which is unintended. Instead, install it into the custom directory if it is set, otherwise install it in the default import library installation directory. Includes a test for this.
8 years ago
shared_library('customdir', 'lib.c',
install : true,
install_dir : get_option('libexecdir'))