Add stdint library for declare unidentified type 'uint8_t' #7241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Hello. I'm a junior developer who has been avidly using this project. I'm delighted to have the opportunity to contribute to this project.
During the process of running 'make PythonAPI' in CARLA 0.9.15.2 version, I encountered an error while building BuildLibCarla.sh.
The error log was as follows:
Upon encountering this error, my initial action was to search for issues related to the 'uint8_t' keyword in the issue section. However, I did not find any issues addressing the specific problem I was facing in my situation.
So, I searched for this error on Google, and I came across a solution at the following link, where the advice was to add the
#include <stdint.h>
header.https://stackoverflow.com/questions/50346142/identifier-uint8-t-is-undefined-visual-studio-2017
Following this advice, I opened the specified file (
carla/LibCarla/source/carla/client/FileTransfer.h
) and added the mentioned header file. I then confirmed that the build process proceeded without any issues.I had no issues building it before, and I'm also not sure why this problem occurred now.
In any case, since it seemed like a problem that needed to be resolved by directly modifying the library, regardless of the individual development environment, I decided to upload the information to the PR section instead of creating an issue.
If there are any aspects I may have overlooked, please feel free to point them out.
Where has this been tested?
Possible Drawbacks