CMakeCache.txt and cmake.check_cache files in VS2017
After getting MuseScore up and running in VS2017, these two files have changed. Git views them as changes too. If I ignore them, then git changes .gitignore, which is also a git file and now git asks me to check in my changes there too. I've undone the .gitignore changes, so I'm back to these two files being changed.
What should I do about this?
Comments
I don't see these in my build. Just remove them?
Edir: I do have them in the mscv.build_x64 directory, but there they do get ignored by git.
In reply to I don't see these in my build by Jojo-Schmitz
They are in these locations in my project dir:
build/CMakeCache.txt
build/CMakeFIles/cmake.check_cache
If you don't have them, that's a weird sign. I believe that VS2017 created them as part of the CMake parsing process. But I am not certain.
In reply to They are in these locations… by sideways
They definitly don't belong there but into the mscv.build_x64 directory
In reply to They definitly don't belong… by Jojo-Schmitz
OK, I just deleted those two. Files of those same names do exist in the _x64 directory too, but they are from yesterday, not today. Something weird must have happened today. I didn't do anything strange, but the whole environment is brand new, so stuff happens.
In reply to OK, I just deleted those two… by sideways
These files keep reappearing when I'm not paying attention. I have deleted them twice, and they have reappeared twice. It's not every time when I open the project. Maybe the first time after a reboot? I haven't pinned it down yet.
In reply to These files keep reappearing… by sideways
It appears to be the first time I open the project after a reboot. Every morning I have to delete these files.
Any idea where this is configured incorrectly? I believe it should probably be editing these same-named files in the msvc.build_x64 directory.
In reply to It appears to be the first… by sideways
Something got to be wrong with your setup, as I don't have these file (at that location)
In reply to Something got to be wrong… by Jojo-Schmitz
Yes, but where do I look to find the problem?
In reply to Yes, but where do I look to… by sideways
no idea, sorry
In reply to no idea, sorry by Jojo-Schmitz
I think I see the real problem now. It's when I open Qt Creator that it creates these files. This morning I opened it out of habit, then closed it. Just now I opened it to edit a .ui file and it created these text files.
In reply to I think I see the real… by sideways
Do you build in both VS2017 and Qt Creator now? Qt Creator is not opening the MuseScore project properly now that I have migrated to 2017. So it creates these two files, but then fails and bails out. I see no project tree, but I can open .ui files from File/Open... and edit them. Is there a way to configure things so both VS2017 and Qt Creator can parse the Makefile?
In reply to Do you build in both VS2017… by sideways
I'm using both and in parallel and on the same repository and without the problems you describe
In reply to I'm using both and in… by Jojo-Schmitz
I think if I want to use Qt and resolve this I need to reconfigure the MuseScore project inside the whole CMake configuration part of Qt Creator. That would probably solve it, since the directories have changed.