-
Notifications
You must be signed in to change notification settings - Fork 8
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
Support for .pro file for QtCreator along with .sln for Visual Studio #9
Comments
Hmm, I just create it by just click create pro file menu as you said, I am not sure if it would perfectly work. |
and if it doesn't work, I am going to change build process (to CMake) in the future. |
As it's tedious to create .pro file again and again when you add or remove files so I think your idea of changing the build process to CMake looks good! |
As CMake is a cross-platform build system generator so I am convinced that Adora should use CMake! |
I am new to cmake, so it would take a long time to change to cmake please be patient |
can you please help me to write CMakeList? I am still learning CMakeList and I don't know how to separate CMakeList for each directory. You can enter my new repository Raina ( where I am changing to CMakeList) and it has root ( Raina - CMakeList) I think lib-ffmpeg/CMakeList looks okay but the problem is I don't know how to configure CMakeList in Ui directory. |
No worries, I have done it.
Oh No worries, I have done it. |
Hey, As you already saw my repo AdoraPlayer and Raina, they are based on CMake. it's currently working well on Windows and Mac OS. I am developing them as video player and video streaming platform. I have no experience linux. in this case if you help me, I will appreciate. |
Can you please create .pro file in Visual Studio(there is option to create .pro file automatically) and include it in Adora repository so that it becomes easy for those who use QtCreator to build Adora? The only thing you need to do extra is to create that .pro file again when you add or remove files.
In fact, I was going to test the latest changes but as neither you have released those changes nor I am able to test it by building Adora in Visual Studio.
The text was updated successfully, but these errors were encountered: