> What was unclear to me is that it now sounds like you are installing two
> distinct files from your repository to the same destination file rather
> than re-installing a modified version of the same file.
Yes, your are right i am doing exactly this
> I think that is conceptually an error prone
On 10/01/2015 10:12 AM, Jörg Kreuzberger wrote:
-Ursprüngliche Nachricht-
Von:Nils Gladitz
Gesendet: Do 01.10.2015 09:40
Betreff:Re: [CMake] cmake install behaviour with git
An: Jörg Kreuzberger ; cmake@cmake.org;
On 10/01/2015 08:35 AM, Jörg Kreuzberger wrote
-Ursprüngliche Nachricht-
Von:Nils Gladitz
Gesendet: Do 01.10.2015 09:40
Betreff:Re: [CMake] cmake install behaviour with git
An: Jörg Kreuzberger ; cmake@cmake.org;
> On 10/01/2015 08:35 AM, Jörg Kreuzberger wrote:
> > This comes from installs, there w
On 10/01/2015 08:35 AM, Jörg Kreuzberger wrote:
This comes from installs, there we install some configuration files with the
builded targets.
e.g. you install a builded executable, together with an config xml file from
SCM.
If you make a product install, you want to "overwrite" the original con
> >
> > Now install behaves differnt, cause cmake checks only file time difference.
> Files previously overwritten are now
> > considered Up-to-date
>
> Why would you want to overwrite files that have not changed?
This comes from installs, there we install some configuration files with the
bu
Hej,
>
> Now install behaves differnt, cause cmake checks only file time difference.
> Files previously overwritten are now
> considered Up-to-date
Why would you want to overwrite files that have not changed?
> Has anyone found a solution for this after a git migration?
We’re using CMake wit
Hi!
the cmake install behaviour of files was ok for me, as long as we used svn.
Now we changed to git and i have a problem now with the install behaviour.
On git the timestamps of all files get the time of the clone. So files not build
(e.g. configuration files, xml files etc) from the repository
