meson/test cases/common/152 shared module resolving.../meson.build

project('shared module resolving symbol in executable', 'c')

# The shared module contains a reference to the symbol 'func_from_executable',
# which is always provided by the executable which loads it.  This symbol can be
# resolved at run-time by an ELF loader.  But when building PE/COFF objects, all
# symbols must be resolved at link-time, so an implib is generated for the
# executable, and the shared module linked with it.
#
# See testcase 125 for an example of the more complex portability gymnastics
# required if we do not know (at link-time) what provides the symbol.

dl = meson.get_compiler('c').find_library('dl', required: false)
e = executable('prog', 'prog.c', dependencies: dl, export_dynamic: true)
m = shared_module('module', 'module.c', link_with: e)
test('test', e, args: m.full_path())
Support implibs for executables on Windows Add a boolean 'implib' kwarg to executable(). If true, it is permitted to use the returned build target object in link_with: On platforms where this makes sense (e.g. Windows), an implib is generated for the executable and used when linking. Otherwise, it has no effect. (Rather than checking if it is a StaticLibrary or SharedLibary, BuildTarget subclasses gain the is_linkable_target method to test if they can appear in link_with:) Also install any executable implib in a similar way to a shared library implib, i.e. placing the implib in the appropriate place Add tests of: - a shared_module containing a reference to a symbol which is known (at link time) to be provided by the executable - trying to link with non-implib executables (should fail) - installing the implib (This last one needs a little enhancement of the installed file checking as this is the first install test we have which needs to work with either MSVC-style or GCC-style implib filenames) 8 years ago			`project('shared module resolving symbol in executable', 'c')`

			`# The shared module contains a reference to the symbol 'func_from_executable',`
			`# which is always provided by the executable which loads it. This symbol can be`
			`# resolved at run-time by an ELF loader. But when building PE/COFF objects, all`
			`# symbols must be resolved at link-time, so an implib is generated for the`
			`# executable, and the shared module linked with it.`
			`#`
			`# See testcase 125 for an example of the more complex portability gymnastics`
			`# required if we do not know (at link-time) what provides the symbol.`

			`dl = meson.get_compiler('c').find_library('dl', required: false)`
Add `export_dynamic` argument to `executable`. (#2662) 7 years ago			`e = executable('prog', 'prog.c', dependencies: dl, export_dynamic: true)`
Support implibs for executables on Windows Add a boolean 'implib' kwarg to executable(). If true, it is permitted to use the returned build target object in link_with: On platforms where this makes sense (e.g. Windows), an implib is generated for the executable and used when linking. Otherwise, it has no effect. (Rather than checking if it is a StaticLibrary or SharedLibary, BuildTarget subclasses gain the is_linkable_target method to test if they can appear in link_with:) Also install any executable implib in a similar way to a shared library implib, i.e. placing the implib in the appropriate place Add tests of: - a shared_module containing a reference to a symbol which is known (at link time) to be provided by the executable - trying to link with non-implib executables (should fail) - installing the implib (This last one needs a little enhancement of the installed file checking as this is the first install test we have which needs to work with either MSVC-style or GCC-style implib filenames) 8 years ago			`m = shared_module('module', 'module.c', link_with: e)`
Use full_path() rather than adding current_build_dir() as rpath in test common/154 8 years ago			`test('test', e, args: m.full_path())`