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

Jucer2CMake output file #632

Open
Xav83 opened this issue May 20, 2020 · 2 comments
Open

Jucer2CMake output file #632

Xav83 opened this issue May 20, 2020 · 2 comments

Comments

@Xav83
Copy link

Xav83 commented May 20, 2020

Hi @McMartin !

I hope everything is going fine for you ! 🙂

I was wondering if it would be possible to have some options in Jucer2Reprojucer to modify the location and the name of the generated file.

We are currently trying to automate all our internal build processes using cmake, and having the possibility to specify the name of the Jucer2Reprojucer generated file (which is currently CMakeLists.txt) would simplify our code.

This would allows use to specify a custom target in cmake which would run Jucer2Reprojucer, from our personal CMakeLists.txt and include the generated file of Jucer2Reprojucer, all in the same folder.

The architecture of files could look like:

root/
  |- CmakeLists.txt (our custom file calling Jucer2Reprojucer and including the generated file)
  |- Project.jucer
  |- Jucer2ReprojucerGeneratedFile.cmake

instead of

root/
  |- CMakeLists.txt (our custom file calling Jucer2Reprojucer and including the generated file)
  |- folder
    |- Project.jucer
    |- CMakeLists.txt (file generated by Jucer2Reprojucer)

This issue is not urgent for us.
Indeed, we are currently cleaning our repository architecture to have something like the second one I put up there, which would be much cleaner than our current folder architecture (our folder architecture is a bit messy 😆).
So if you have any suggestions or other solutions, I am all ears 🙂

Thanks for your work on FRUT and for you attention to this issue.
Have a great day 🙂

@McMartin
Copy link
Owner

Hi @Xav83,

Sorry for the late reply. Everything is going fine for me, and I hope the same for you and the @Expressivee team!

I have planned for quite some time to add an option to Jucer2Reprojucer to choose in which folder the CMakeLists.txt file is generated (instead of in the current working directory by default), but I hadn't considered giving the possibility to also choose the filename.

However, I have also planned to support writing the contents of the CMakeLists.txt file to the standard output. You could then use that feature to write to a file with whatever name that makes it more convenient for you.

I don't know when I'll work on adding these options/features, but I'll keep you posted!

@McMartin McMartin changed the title Jucer2Reprojucer output file Jucer2CMake output file Mar 6, 2022
@McMartin
Copy link
Owner

McMartin commented Mar 6, 2022

I reworded the title of this issue since Jucer2Reprojucer was deprecated in favor of Jucer2CMake in #645, then removed in #701.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants