| 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: Andreas Grabher <andreas_g86@xxxxxxxxxx>
- Date: Fri, 2 Apr 2021 09:54:21 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; t=1617350065; bh=xbD+gBHfcYmapoLuygRvw5Iq19BcNz6a0um67WZSLBQ=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=iiK4O/cTN2dshR+FTbc7WzRMMFbYGD7va98hemFtC11cuCf48ZFZzsv+pvhvVBP1N 1LsYqpFlJqpC+IFaTY1jDi4ZLom9YtHyiKE6E9l1BC8bcb9J73hO3GIzCQpX2q0fFe iSJUFbijTiqqov90IVdW0U++SuLK3G6lZVuOYjsxcZVgp43h4d8OHzZE3EH3HjtHEp s0I9rp5U5/IudTL3Z1eYbuQleqKJCGdTXl8SUeys7jQSI4NWu0aQkEmP6ngfmUpluE bpZa24/5W/WE3RlcgxTZkEodC6lH0sMKiDvrdU/L/wAbng+Syf/1YXaT3ARvmqmoOQ aJIasfDPuvHKw==
Thank you Thomas and Chang for the answers! For some reason I got confused because „cmake“ gave an error while „cmake -G Xcode“ just gave a warning. I avoided the error by using „cmake .“ but didn’t expect this to be the solution for the warnings with „cmake -G Xcode“ because i thought these were two different problems.
Is this input a correct implementation of Bob C’s workflow?
mkdir -p builddir
cmake -G <generator> -S . -B builddir
cmake --build
> Am 31.03.2021 um 18:59 schrieb Chang Chong <codemonkey2x@xxxxxxxxx>:
>
> I would recommend you create a build directory like Bob C. One of the nice features of cmake is that it helps with performing out of source builds. It could be a matter of personal preference, but this keeps the source tree clean and puts all the artifacts co-located in their own directory rather than intermixed with your source.
>
> sample workflow based on Bob C’s post would be ..
>
> # cmake -G <generator> -S <path/to/src> -B <path/to/build>
> # cmake --build <path/to/build>
>
>
>
>> On Mar 31, 2021, at 1:29 AM, Thomas Huth <th.huth@xxxxxxxxx> wrote:
>>
>> 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
>>>>>
>>
>>
>
>
>