Re: [hatari-devel] Cmake warning |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Cmake warning
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Wed, 31 Mar 2021 08:29:43 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1617172185; bh=LmSj7acc6tU7p/ZVqlVmDqfDU6Myq5ipgENep8/ueBA=; h=Date:From:To:Subject:From; b=oVtYOorTWqPg1zEQlpfKCQVyfQb0L/VzvENcXevXBDvgMRaBOhDEoOmvxifRnIkf/ F6yMwImDt3m1wbV/A8KYIbBrfjjt2XHoauUgpnOWI/MfQCdPO0Kl/0qyB0xPWI4hlV o95TtB/QVXJm1Df/abMrgTe7n5Lzgt0rNl1ODJCHg2mkQZm+rcJNRvKRd8xBTSqX4D nnUJfcym9wkP01T+ViK6UDS48wwLJdKSWU4VURwXB2ONW5LQ4BsrpBGW0yT4EWcGGf GjXYs9GS9/EoPmpaYsoLbGVY5DhS4xcdKpSO+bO2wm2d8XfRS1DRXR3B1N7/TF2rCK qfDOlwdrNjqMA==
Am Sun, 21 Mar 2021 18:31:33 +0100
schrieb Andreas Grabher <andreas_g86@xxxxxxxxxx>:
> Thank you for the explanation. Is there no other way to do this? e.g.
> hardcode them in cmakelists.txt?
I think it should be enough to provide the path to either the source or
the build directory:
cmake -G Xcode .
So that's just one additional dot at the end - not too much to type, I
hope ;-)
Thomas
>
> > Am 21.03.2021 um 17:41 schrieb Bob Carpenter <hatari@xxxxxxxxxx>:
> >
> > Andreas,
> >
> > That is a change to Cmake. I had to update my Hatari compiling to
> > instructions to say this: cmake -G Xcode -S <path-to-source> -B
> > <path-to-build>
> >
> > When you do this and provide the directory paths, Cmake will no
> > longer give you this warning. I think the most recent version of
> > Cmake will give you an error if you do not provide the -S and -B
> > arguments.
> >
> > Bob C
> >
> >> On Sun, Mar 21, 2021 at 8:01 AM Andreas Grabher
> >> <andreas_g86@xxxxxxxxxx> wrote: When generating an Xcode project
> >> from the latest Hatari sources using Cmake (cmake -G Xcode) I get
> >> this warning:
> >>
> >> CMake Warning:
> >> No source or binary directory provided. Both will be assumed to
> >> be the same as the current working directory, but note that this
> >> warning will become a fatal error in future CMake releases.
> >>
> >> Does anyone have an idea how to fix this?
> >>
> >> Best wishes,
> >> Andreas
> >>