SDK Setup for dummies

[Ben Wood]

Hi Kenley


Xcode location settings look fine
Command Line Tools: Xcode 15.2(15C500b)

Here's the Conan setting and profile

https://mab.to/t/Syf3u8e3PMU/eu1

Thanks for your continued support

[Ben Wood]

I tried installing conan from terminal and then listing profiles
It didn't list anything so I used the detect command

detect_api: Found apple-clang 15.0
detect_api: apple-clang>=13, using the major as version

Detected profile:
[settings]
arch=x86_64
build_type=Release
compiler=apple-clang
compiler.cppstd=gnu17
compiler.libcxx=libc++
compiler.version=15
os=Macos

WARN: This profile is a guess of your environment, please check it.
WARN: Defaulted to cppstd='gnu17' for apple-clang.
WARN: The output of this command is not guaranteed to be stable and can change in future Conan versions.
WARN: Use your own profile files for stability.
Saving detected profile to /Users/monterey/.conan2/profiles/default

[kenley_m]

Hi Ben,

As a further diagnostic step could you capture stdout and stderr from the build script. I'd like to see if there are any further clues as to why the compiler setting doesn't seem to be in the profile at the time the build is proceeding.

I noticed in your latest post conan configuration files were in a ".conan2". Is that just a secondary conan home location created for your command line installation experiment?

--Kenley

[Ben Wood]

Maybe the conan2 folder was from me forcing Conan to reinstall but I really have no idea.
I've found the Conan folder so I'll link that.

https://mab.to/t/PvFFA0P6cik/eu1

Thanks Kenley

[kenley_m]

Hi Ben,

Thanks for sending over the conan folder. That confirms your default profile (~/.conan/profiles/default) is missing several key items. Please delete the profile and re-run the build. During the build conan will find that the default profile is missing and automatically try to detect the defaults again. This time it should see your currently selected command line tools and set the appropriate values. For this run please capture stdout and stderr of the build script in a file and send it if there are still any issues.

If you're not sure of how to capture the output and also see it on the command line you could run it using a syntax like the following (assuming you're in the root of your sdk package):

python3 setup/build_cpp_ptsl_sdk.py -t ptsl.client.cpp 2>&1 | tee build.log

[Ben Wood]

Thanks Kenley.
That did the trick, I successfully built the client wrapper and PTSLCMD.
Thanks for all your help

[kenley_m]

Glad to see things are working better now! Thanks for your reply.