Skip to content
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

not generate *.hex file in using cmake on CLI #4

Open
HY-PARK opened this issue Sep 20, 2019 · 2 comments
Open

not generate *.hex file in using cmake on CLI #4

HY-PARK opened this issue Sep 20, 2019 · 2 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@HY-PARK
Copy link

HY-PARK commented Sep 20, 2019

I used cmake on CLI(Command Line Interface).
Build is finished successfully but I couldn't find the *.hex file

$ cd {TESuit Project} && mkdir build && cd build
$ cmake ..

below picture is the result of stand-alone build
image

below picture is the result of CLion build button
image

If we can build with cmake command we will add CI for build test or unit test and we do not need to use the same IDE.

@HY-PARK
Copy link
Author

HY-PARK commented Sep 20, 2019

I found the reason.
because TESuit/arch/avr8.postbuild.cmake file has absolute path.
like this

${CMAKE_CURRENT_SOURCE_DIR}/cmake-build-debug/${PROJECT_NAME}

I think that we need to make more efficient cmake structure.

@GabrielKim GabrielKim added bug Something isn't working good first issue Good for newcomers labels Sep 22, 2019
@GabrielKim
Copy link
Collaborator

This problem now occurs when there was no structural plan, starting simply at first.
I'll revise the structure of the path from "Target Postbuild script".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants