-
Notifications
You must be signed in to change notification settings - Fork 97
General Query #358
Comments
When you open a file, a search is made for the top level CMakeLists.txt or for instance meson.build. If it is found, the project path is set to the directory where this CMakeLists.txt was found. Working with a very large project is troublesome using libclang, but given that you have a very decent computer, the main issue is file IO I think. Both |
I have not yet been able to open an existing directory with a CMakeLists.txt and having it recognised as a project. I can open a directory and see all the files, but I cannot build as jucipp says "Could not find a supported project". |
@matsbror Could you post a top level CMakeLists.txt file that is not working? Also, what OS are you on? One issue I can think of could be if the CMakeLists.txt file contains Windows newlines (\r\n instead of \n), but I think I solved this issue some months back. |
Also, when identifying the top-level CMakeLists.txt, juCi++ looks for a line with |
Thanks for the reply. The setting of |
In the past i have tried this project on MSYS2 and failed to get the App to launch properly (issue with GTK).
I am now going back to Linux and want to retry the App as it looks interesting and i might want to use and contribute to it.
Can you tell me once the App is launched can you point it at its own CMakeList.txt and then start browsing the project/App ?
There are probably two sub questions contained this question;
o Is the starting point for browsing an existing project its top level CMakeLists.txt file ?
o Is Jucipp upto the job of of browsing a project that links to a huge library like GTK/GTKMM ?
The text was updated successfully, but these errors were encountered: