summaryrefslogtreecommitdiffstats
path: root/platforms/ptxdist-version.in
Commit message (Collapse)AuthorAgeFilesLines
* kconfig: 'option env' is goneMichael Olbrich2019-05-101-5/+1
| | | | | | Instead '$(ENV_VARNAME)' can be used directly. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
* platforms: simplify platforms/KconfigMichael Olbrich2014-02-251-0/+1
| | | | | | This makes it easier to customize the platform. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
* [ptxdist] rework version generationMarc Kleine-Budde2010-04-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch aims to fix some problems of the version handling of ptxdist which were introducted with switching to timed releases: a) The version is specified in "configure.ac", the "local version" ("00003-gbf29f16") is generated by "setlocalversion". "setlocalversion" generates it's ouput relative to the latest tag. This leads to strange version strings, after creating a tag, and forgetting to run "./autogen.sh && ./configure && make". b) The ptxdist created with a "make dist", even if a not tagged version, always thinks it's a release. c) BSPs working with "master" need a migrate after each release. Because the compatibility checker uses year and month. The problems are^Wshould be fixed with these changes: a) "setlocalversion" now generates the whole full version, e.g.: "2010.04.0-00003-gbf29f16". "configure.ac" uses "m4_esyscmd" to figure out the current version while running "configure". (Yes, "configure"). b) A file ".tarball-version" is added to the tarball to track the version while creating the tarball (same goes for the installation). "setlocalversion" will use the version information from ".tarball-version" c) If both ptxdist and config file are not using a release, i.e. their versions an "appendix", we say it's compatibe, too. Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
* [ptxdist] adopt config file version handling to cope with dynamic fullversionMarc Kleine-Budde2010-01-061-0/+9
In the past ptxdist's fullversion was replaced by configure in these files: - platforms/ptxdist-version.in.in (PLATFORMCONFIG_VERSION) - rules/ptxdist-version.in.in (CONFIGFILE_VERSION) resulting in: - platforms/ptxdist-version.in - rules/ptxdist-version.in However the fullversion is rather dynamic now since it can hold version information from the version control system. ptxdist refuses to run if the versions don't match. During development this may change quite often which is probably too annoying for the developers. This patch introduces two new version variables: - PTXDIST_VERSION_CFG_SCM - PTXDIST_VERSION_CFG_FULL The _SCM variable holds "-git" if ptxdist isn't release. For released versions _SCM is empty. PTXDIST_VERSION_CFG_FULL contains '$year.$month.$bugfix$scm' (scm is PTXDIST_VERSION_CFG_SCM), for example: '2010.01.0-git' for modifies i.e. dirty '2010.01.0' release. Further we don't no longer modify the "*/ptxdist-version.in.in", we use the kconfig 'option env="VAR"' to get the correct version from the environment. Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>