folkslinux
/
rpm
mirror of https://github.com/rpm-software-management/rpm.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
rpm/platform.in

115 lines
3.4 KiB
Plaintext
Raw Normal View History

- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
# Per-platform rpm configuration file.
#==============================================================================
# ---- per-platform macros.
#
Differentiate autoconf processed replacements from our own Some of the replacements in platform.in are expected to be processed by the build system configuration file, whereas others are replaced by installplatform at the time of install. Use =VAR= notation instead of @VAR@ to differentiate the latter from the former. No functional changes, just makes it easier to understand and handle.
2022-06-13 16:52:08 +08:00
%_arch =RPMCANONARCH=
%_build_arch =RPMCANONARCH=
- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
%_vendor @RPMCANONVENDOR@
%_os @RPMCANONOS@
Differentiate autoconf processed replacements from our own Some of the replacements in platform.in are expected to be processed by the build system configuration file, whereas others are replaced by installplatform at the time of install. Use =VAR= notation instead of @VAR@ to differentiate the latter from the former. No functional changes, just makes it easier to understand and handle.
2022-06-13 16:52:08 +08:00
%_gnu =RPMRC_GNU=
- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
%_target_platform %{_target_cpu}-%{_vendor}-%{_target_os}
Differentiate autoconf processed replacements from our own Some of the replacements in platform.in are expected to be processed by the build system configuration file, whereas others are replaced by installplatform at the time of install. Use =VAR= notation instead of @VAR@ to differentiate the latter from the former. No functional changes, just makes it easier to understand and handle.
2022-06-13 16:52:08 +08:00
%optflags =RPMRC_OPTFLAGS=
- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
Differentiate autoconf processed replacements from our own Some of the replacements in platform.in are expected to be processed by the build system configuration file, whereas others are replaced by installplatform at the time of install. Use =VAR= notation instead of @VAR@ to differentiate the latter from the former. No functional changes, just makes it easier to understand and handle.
2022-06-13 16:52:08 +08:00
%__isa_name =ISANAME=
%__isa_bits =ISABITS=
First crack at adding ISA provides to packages (rhbz#235755) - Horrible kludgery to get the isa names and bits into platform specific macros from installplatform script. That beast needs to die. I mean really - In build, add provides: name(isa) = evr automatically when it makes sense (similarly to name = evr provides). ISA consists of ISA name and bitness (or wordsize). This can be used to correctly express multilib dependencies without resorting to (expensive!) file dependency kludges, eg for dlopen()'ed libraries where automatic dep extraction doesn't force dependency on 32bit vs 64bit version, you can now use: Requires: foo-plugin%{?_isa} This expands to foo-plugin(x86-32) for i?86 packages, foo-plugin(x86-64) to x86_64 etc, and permits spec to be shared with older distros which don't have ISA provides. - The same could be expressed with "canon arch" just as well, but using the ISA to differentiate from %_arch and the like: eg i386 could be used instead of x86-32 but it's overloaded with meanings (the actual i386 processor vs i386 compatible cpu family etc)
2008-04-11 00:36:03 +08:00
%__isa %{__isa_name}-%{__isa_bits}
Push platform config out of main rpm macros file - canon arch & color stuff is now calculated per each known arch in installplatform, and just a single place where arch name mangling is done
2011-03-25 20:39:36 +08:00
# The default transaction color. This value is a set of bits to
# determine file and dependency affinity for this arch.
# 0 uncolored (i.e. use only arch as install hint)
# 1 Elf32 permitted
# 2 Elf64 permitted
Differentiate autoconf processed replacements from our own Some of the replacements in platform.in are expected to be processed by the build system configuration file, whereas others are replaced by installplatform at the time of install. Use =VAR= notation instead of @VAR@ to differentiate the latter from the former. No functional changes, just makes it easier to understand and handle.
2022-06-13 16:52:08 +08:00
%_transaction_color =RPMCANONCOLOR=
Push platform config out of main rpm macros file - canon arch & color stuff is now calculated per each known arch in installplatform, and just a single place where arch name mangling is done
2011-03-25 20:39:36 +08:00
- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
#==============================================================================
# ---- configure macros.
#
%_prefix @prefix@
%_exec_prefix @exec_prefix@
%_bindir @bindir@
%_sbindir @sbindir@
%_libexecdir @libexecdir@
Add datarootdir.
2007-09-05 13:52:26 +08:00
%_datarootdir @datarootdir@
- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
%_datadir @datadir@
%_sysconfdir @sysconfdir@
%_sharedstatedir @sharedstatedir@
%_localstatedir @localstatedir@
Differentiate autoconf processed replacements from our own Some of the replacements in platform.in are expected to be processed by the build system configuration file, whereas others are replaced by installplatform at the time of install. Use =VAR= notation instead of @VAR@ to differentiate the latter from the former. No functional changes, just makes it easier to understand and handle.
2022-06-13 16:52:08 +08:00
%_lib =LIB=
%_libdir @exec_prefix@/=LIB=
- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
%_includedir @includedir@
%_oldincludedir @oldincludedir@
%_infodir @infodir@
%_mandir @mandir@
Fix missspelling in macro name (_initddir -> _initrddir), thanks to - Ville Skyttä - old macro with typo is kept for compatiblity
2008-06-30 18:23:42 +08:00
%_initddir %{_sysconfdir}/rc.d/init.d
# Deprecated misspelling, present for backwards compatibility.
%_initrddir %{_initddir}
Add a %_rundir macro to the platform files. The default value is /run, it can be changed with the --with-rundir configure option. Signed-off-by: Panu Matilainen <pmatilai@redhat.com>
2014-05-07 14:12:46 +08:00
%_rundir @RUNDIR@
- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
Kick out the dumb defaultdocdir logic from installplatform - defaultdocdir is simply %{_datadir}/doc
2008-10-17 13:11:10 +08:00
%_defaultdocdir %{_datadir}/doc
Move noLang to rpmlib. Add defaultdocdir to per-platform macros. CVS patchset: 3788 CVS date: 2000/06/01 05:36:14
2000-06-01 13:36:14 +08:00
Make CPU limit for building configurable through _smp_ncpus_max macro - Makes the max number of cpu's used by %{_smp_mflags} configurable on spec, user or system level. - Originally reported as RhBug:669638 and included in redhat-rpm-config in RHEL/Fedora, but makes sense to have generally available.
2014-01-22 16:49:56 +08:00
# Maximum number of CPU's to use when building, 0 for unlimited.
#%_smp_ncpus_max 0
Isolate %_smp_build_ncpus and use it for %_smp_mflags. Refactor _smp_build_ncpus and use it in %_smp_mflags. Note that now having a single CPU, %_smp_mflags is expanded to '-j1'.
2018-11-28 17:52:01 +08:00
%_smp_build_ncpus %([ -z "$RPM_BUILD_NCPUS" ] \\\
Use %getncpus for %_smp_mflags and %_lto_cflags to make them affinity-aware Making %_smp_mflags affinity-aware was requested long, long ago in https://bugzilla.redhat.com/show_bug.cgi?id=891588 but somewhere along it fell in the cracks between distro versions...
2019-01-15 17:40:56 +08:00
&& RPM_BUILD_NCPUS="%{getncpus}"; \\\
Make CPU limit for building configurable through _smp_ncpus_max macro - Makes the max number of cpu's used by %{_smp_mflags} configurable on spec, user or system level. - Originally reported as RhBug:669638 and included in redhat-rpm-config in RHEL/Fedora, but makes sense to have generally available.
2014-01-22 16:49:56 +08:00
ncpus_max=%{?_smp_ncpus_max}; \\\
if [ -n "$ncpus_max" ] && [ "$ncpus_max" -gt 0 ] && [ "$RPM_BUILD_NCPUS" -gt "$ncpus_max" ]; then RPM_BUILD_NCPUS="$ncpus_max"; fi; \\\
Isolate %_smp_build_ncpus and use it for %_smp_mflags. Refactor _smp_build_ncpus and use it in %_smp_mflags. Note that now having a single CPU, %_smp_mflags is expanded to '-j1'.
2018-11-28 17:52:01 +08:00
echo "$RPM_BUILD_NCPUS";)
Drop double-quotes from %_smp_mflags and %_lto_cflags The double-quotes got added in e811c7ec0b4d2685b63b61803e3952466b1a4ac6 and 2bb7b0cf066c97a9d92eb0bf59618896000cb29d but traditionally there have been no quotes around %_smp_mflags output, to avoid risking any breakage due to such a simple thing, lets go back to how it used to be.
2019-01-15 17:47:29 +08:00
%_smp_mflags -j%{_smp_build_ncpus}
- fix: adjust arg count for --POPTdesc/--POPTargs deletion. - add linux per-platform macro %_smp_mflags <sopwith@redhat.com>. - document more popt aliases for --help usage. - remove --tarbuild from man page(s), use -t[abpcils] instead (#48666). CVS patchset: 4936 CVS date: 2001/07/11 14:23:01
2001-07-11 22:23:01 +08:00
Cap number of threads on 32bit platforms, add tunables (RhBug:1729382) On 32bit plaforms, address space is easily exhausted with multiple threads, causing arbitrary builds failure regressions (RhBug:1729382). Simply cap the number of threads to maximum of four on any 32bit platform to play it safe. It's still three more than we were able to use on older releases... In addition, introduce tunables for controlling the number of threads used similarly to what is available for number of CPUs: forced number and a separate ceiling. The max logic gets surprisingly tricky with the mixed OMP and rpm tunables and different semantics. Notably, OMP does not have a nice way to set a maximum from inside a program (this is only possible from an environment variable so we can't use it here), so we need to jump through a lot of hoops to figure out whether an *unlimited* setting would go above the platform limitation. I'm not entirely convinced this is 100% bulletproof, but then it's all going to change and become even more complicated when we start taking memory limitations into account...
2019-08-23 16:17:21 +08:00
# Maximum number of threads to use when building, 0 for unlimited
#%_smp_nthreads_max 0
%_smp_build_nthreads %{_smp_build_ncpus}
- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
#==============================================================================
# ---- Build policy macros.
#
platform: Ensure empty buildroot for %install This change ensures that any existing buildroot contents are wiped and a fresh empty one is created for usage in %install. Variations of this exist in virtually every RPM-based Linux distribution for more than a decade. At this point, it is expected behavior everywhere and it is amazing that it has not yet been put in RPM itself until now... Credit goes to Michael Schroeder from openSUSE for the original work and Tom Calloway for the variant adapted for Fedora that is the basis for this change.
2020-02-03 01:18:23 +08:00
#---------------------------------------------------------------------
# Expanded at beginning of %install scriptlet.
#
%__spec_install_pre %{___build_pre}\
%{__rm} -rf "%{buildroot}"\
%{__mkdir_p} "%{dirname:%{buildroot}}"\
%{__mkdir} "%{buildroot}"\
%{nil}
Yet another patial harlink set fix. CVS patchset: 4903 CVS date: 2001/06/25 20:01:42
2001-06-26 04:01:42 +08:00
#---------------------------------------------------------------------
# Expanded at end of %install scriptlet.
- fix: filter excluded paths before adding install prefixes (#8709). - add i18n lookaside to PO catalogue(s) for i18n strings. - try for /etc/rpm/macros.specspo so that specspo autoconfigures rpm. - per-platform configuration factored into /usr/lib/rpm subdir. CVS patchset: 3588 CVS date: 2000/02/25 16:29:44
2000-02-26 00:29:44 +08:00
#
- change optflags for i386. - multilib patch, take 1. CVS patchset: 3920 CVS date: 2000/07/05 20:39:15
2000-07-06 04:39:15 +08:00
Differentiate autoconf processed replacements from our own Some of the replacements in platform.in are expected to be processed by the build system configuration file, whereas others are replaced by installplatform at the time of install. Use =VAR= notation instead of @VAR@ to differentiate the latter from the former. No functional changes, just makes it easier to understand and handle.
2022-06-13 16:52:08 +08:00
%__arch_install_post =ARCH_INSTALL_POST=
- add RPMTAG_OPTFLAGS, configured optflags when package was built. - add RPMTAG_DISTURL for rpmfind-like tools (content unknown yet). - teach brp-compress about /usr/info and /usr/share/info as well. - update macros.in from rpm-4.0 (w/o dbi configuration). CVS patchset: 3878 CVS date: 2000/06/20 21:45:50
2000-06-21 05:45:50 +08:00
Macroize build root policies for consistent disable/override ability Add a separate macro for each brp we have, using standard naming convention and conditionalize the usage in %__os_install_post. Voilà, we have a standard way to disable (and also override) any brp scripts from specs that need it and a common scheme for new brps to follow. Note that this is not supposed to change the existing behavior and default build root policy invocations at all, any change in those would be a thinko/typo/copy-paste error in this commit.
2018-01-18 17:07:05 +08:00
# Standard brp-macro naming:
# convert all '-' in basename to '_', add two leading underscores.
Take %_prefix into account when compressing man pages etc, take II brp-compress used to be all hardcoded around /usr for no good reason. Support passing prefix as an argument and only look for things to compress there. First attempt in 5e65f92b53ca07c6e30921688c1b84d0a6b41db7 had an embarrassing typo/thinko/case of missing brain in the assign syntax. Based on feedback and work of Owen Taylor and Yanko Kaneti in PR #538
2018-10-01 20:37:48 +08:00
%__brp_compress %{_rpmconfigdir}/brp-compress %{?_prefix}
Macroize build root policies for consistent disable/override ability Add a separate macro for each brp we have, using standard naming convention and conditionalize the usage in %__os_install_post. Voilà, we have a standard way to disable (and also override) any brp scripts from specs that need it and a common scheme for new brps to follow. Note that this is not supposed to change the existing behavior and default build root policy invocations at all, any change in those would be a thinko/typo/copy-paste error in this commit.
2018-01-18 17:07:05 +08:00
%__brp_strip %{_rpmconfigdir}/brp-strip %{__strip}
%__brp_strip_comment_note %{_rpmconfigdir}/brp-strip-comment-note %{__strip} %{__objdump}
%__brp_strip_static_archive %{_rpmconfigdir}/brp-strip-static-archive %{__strip}
Add a build root policy for removing executable bits from shared libraries Rpm has traditionally used executable bit on files to determine whether requires for that file should be generated, but the downside is that we have systems full of executable files that cannot actually be executed. When available, use eu-elfclassify to determine files that are pure, non-executable shared objects and remove executable bits from them as a buildroot policy. This preserves the traditional behavior wrt dependency generation but gets rid of the unwanted executable bits.
2020-10-12 18:00:41 +08:00
%__brp_elfperms %{_rpmconfigdir}/brp-elfperms
Add brp-remove-la-files script .la files are libtool files and should generally not be installed. Tons of spec files contain a 'find' command to remove them. Add a helper script that automatically removes all .la files from the build root and let projects that need them opt out of this instead.
2021-05-07 18:11:31 +08:00
%__brp_remove_la_files %{_rpmconfigdir}/brp-remove-la-files
Macroize build root policies for consistent disable/override ability Add a separate macro for each brp we have, using standard naming convention and conditionalize the usage in %__os_install_post. Voilà, we have a standard way to disable (and also override) any brp scripts from specs that need it and a common scheme for new brps to follow. Note that this is not supposed to change the existing behavior and default build root policy invocations at all, any change in those would be a thinko/typo/copy-paste error in this commit.
2018-01-18 17:07:05 +08:00
- add RPMTAG_OPTFLAGS, configured optflags when package was built. - add RPMTAG_DISTURL for rpmfind-like tools (content unknown yet). - teach brp-compress about /usr/info and /usr/share/info as well. - update macros.in from rpm-4.0 (w/o dbi configuration). CVS patchset: 3878 CVS date: 2000/06/20 21:45:50
2000-06-21 05:45:50 +08:00
%__os_install_post \
Macroize build root policies for consistent disable/override ability Add a separate macro for each brp we have, using standard naming convention and conditionalize the usage in %__os_install_post. Voilà, we have a standard way to disable (and also override) any brp scripts from specs that need it and a common scheme for new brps to follow. Note that this is not supposed to change the existing behavior and default build root policy invocations at all, any change in those would be a thinko/typo/copy-paste error in this commit.
2018-01-18 17:07:05 +08:00
%{?__brp_compress} \
Add a build root policy for removing executable bits from shared libraries Rpm has traditionally used executable bit on files to determine whether requires for that file should be generated, but the downside is that we have systems full of executable files that cannot actually be executed. When available, use eu-elfclassify to determine files that are pure, non-executable shared objects and remove executable bits from them as a buildroot policy. This preserves the traditional behavior wrt dependency generation but gets rid of the unwanted executable bits.
2020-10-12 18:00:41 +08:00
%{?__brp_elfperms} \
Macroize build root policies for consistent disable/override ability Add a separate macro for each brp we have, using standard naming convention and conditionalize the usage in %__os_install_post. Voilà, we have a standard way to disable (and also override) any brp scripts from specs that need it and a common scheme for new brps to follow. Note that this is not supposed to change the existing behavior and default build root policy invocations at all, any change in those would be a thinko/typo/copy-paste error in this commit.
2018-01-18 17:07:05 +08:00
%{?__brp_strip} \
%{?__brp_strip_static_archive} \
%{?__brp_strip_comment_note} \
Add brp-remove-la-files script .la files are libtool files and should generally not be installed. Tons of spec files contain a 'find' command to remove them. Add a helper script that automatically removes all .la files from the build root and let projects that need them opt out of this instead.
2021-05-07 18:11:31 +08:00
%{?__brp_remove_la_files} \
- add RPMTAG_OPTFLAGS, configured optflags when package was built. - add RPMTAG_DISTURL for rpmfind-like tools (content unknown yet). - teach brp-compress about /usr/info and /usr/share/info as well. - update macros.in from rpm-4.0 (w/o dbi configuration). CVS patchset: 3878 CVS date: 2000/06/20 21:45:50
2000-06-21 05:45:50 +08:00
%{nil}
Hi! I'd like to start building sparc64 packages (eventhough the install rule details are yet to be designed - IMHO if 64bit SPARC userland is going into 7.0 we should rebuild all packages into 64bit in the next months or so to have time to chase bugs etc.), and this is about what I need. Basically I'd like to have %{_lib} to stand for the last part (normally "lib") of dirname for directories like /lib, /usr/lib, /usr/X11R6/lib because on sparc64-linux they are /lib64, /usr/lib64, /usr/X11R6/lib64 (and on Solaris /lib/sparcv9, /usr/lib/sparcv9 etc.), so that one can use things like /usr/%{_lib} in the spec files. Another thing which I need is an arch specific build root policy. This patch does a few things: 1) add installplatform into EXTRA_DIST files, so that it is actually invoked during rpm build not from CVS 2) Define %_lib lib and let target specific macros override it 3) Split __spec_install_post into __arch_install_post and __os_install_post, --buildpolicy now specifies the __os_install_post part only. spec files can still override the __arch_install_post if the want to. brp-sparc64-linux is used to move 64bit libraries to */lib64 directories from */lib directories if make install of some package left them there. 4) Change installplatform so that on sparc* it creates both sparc and sparc64 target macro dirs (/usr/lib/rpm/sparc{,64}-redhat-linux in sparc*-redhat-linux case). CVS patchset: 3685 CVS date: 2000/04/19 16:03:49
2000-04-20 00:03:49 +08:00
%__spec_install_post\
- add a macro to create a sub-package with debugging symbols. CVS patchset: 5662 CVS date: 2002/08/22 19:21:14
2002-08-23 03:21:14 +08:00
%{?__debug_package:%{__debug_install_post}}\
Yet another patial harlink set fix. CVS patchset: 4903 CVS date: 2001/06/25 20:01:42
2001-06-26 04:01:42 +08:00
%{__arch_install_post}\
%{__os_install_post}\
Hi! I'd like to start building sparc64 packages (eventhough the install rule details are yet to be designed - IMHO if 64bit SPARC userland is going into 7.0 we should rebuild all packages into 64bit in the next months or so to have time to chase bugs etc.), and this is about what I need. Basically I'd like to have %{_lib} to stand for the last part (normally "lib") of dirname for directories like /lib, /usr/lib, /usr/X11R6/lib because on sparc64-linux they are /lib64, /usr/lib64, /usr/X11R6/lib64 (and on Solaris /lib/sparcv9, /usr/lib/sparcv9 etc.), so that one can use things like /usr/%{_lib} in the spec files. Another thing which I need is an arch specific build root policy. This patch does a few things: 1) add installplatform into EXTRA_DIST files, so that it is actually invoked during rpm build not from CVS 2) Define %_lib lib and let target specific macros override it 3) Split __spec_install_post into __arch_install_post and __os_install_post, --buildpolicy now specifies the __os_install_post part only. spec files can still override the __arch_install_post if the want to. brp-sparc64-linux is used to move 64bit libraries to */lib64 directories from */lib directories if make install of some package left them there. 4) Change installplatform so that on sparc* it creates both sparc and sparc64 target macro dirs (/usr/lib/rpm/sparc{,64}-redhat-linux in sparc*-redhat-linux case). CVS patchset: 3685 CVS date: 2000/04/19 16:03:49
2000-04-20 00:03:49 +08:00
%{nil}
- add RPMTAG_OPTFLAGS, configured optflags when package was built. - add RPMTAG_DISTURL for rpmfind-like tools (content unknown yet). - teach brp-compress about /usr/info and /usr/share/info as well. - update macros.in from rpm-4.0 (w/o dbi configuration). CVS patchset: 3878 CVS date: 2000/06/20 21:45:50
2000-06-21 05:45:50 +08:00
Differentiate autoconf processed replacements from our own Some of the replacements in platform.in are expected to be processed by the build system configuration file, whereas others are replaced by installplatform at the time of install. Use =VAR= notation instead of @VAR@ to differentiate the latter from the former. No functional changes, just makes it easier to understand and handle.
2022-06-13 16:52:08 +08:00
=apple=#---------------------------------------------------------------------
=apple=# Apple Darwin vendor specific macros
=apple=#
=apple=%_use_internal_dependency_generator 0
=apple=%__so dylib