-
Notifications
You must be signed in to change notification settings - Fork 16
Updated README.rst for later qi versions #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: team/platform/dev
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -57,7 +57,7 @@ following way: | |
.. code-block:: console | ||
|
||
# install/upgrade Conan 2 | ||
pip install --upgrade conan~=2 | ||
pip install --upgrade conan==2.10 | ||
# create a default profile | ||
conan profile detect | ||
|
||
|
@@ -75,7 +75,7 @@ first get and export the `libqi` recipe into your local Conan cache. | |
|
||
# GitHub is available, but you can also use internal GitLab. | ||
QI_REPOSITORY="https://github.com/aldebaran/libqi.git" | ||
QI_VERSION="4.0.1" # Checkout the version your project need. | ||
QI_VERSION="4.0.3" # Checkout the version your project need. | ||
QI_PATH="$HOME/libqi" # Or whatever path you want. | ||
git clone \ | ||
--depth=1 `# Only fetch one commit.` \ | ||
|
@@ -87,7 +87,7 @@ first get and export the `libqi` recipe into your local Conan cache. | |
# versions of libqi require it | ||
# because of a bug. | ||
|
||
You can then install the `libqi-python` dependencies in Conan. | ||
You need to navigate to the ``${HOME}/libqi`` directory and install libqi dependencies. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's not exactly correct. The There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ahhh makes sense. |
||
|
||
.. code-block:: console | ||
|
||
|
@@ -110,6 +110,14 @@ calling: | |
|
||
cmake --list-presets | ||
|
||
Navigate back to the ``libqi-python`` directory | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You're completely right. The instructions below are about building libqi-python native code for development or testing purposes, and not building the wheel. So there should be a section on the same level as the "Wheel" once below. It's not that much about building "C++ bindings", it's just a different process and purpose. |
||
|
||
Now from here you have two options, either to develop the project with only **C++** bindings or | ||
as a **wheel** to run with python | ||
|
||
C++ Bindings | ||
------------ | ||
|
||
Here, we'll assume that the preset is named `conan-linux-x86_64-gcc-debug`. | ||
To start building, you need to configure with CMake and then build: | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The previous version was wrong indeed (~=2 does not seem to work with pip install), but I think I'd prefer suggesting any Conan version above 2.10:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will make the update to pull request