-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
windows binary release #98
Comments
Sure, someone needs to just do it. Want to? I don’t have windows. |
I've started to port projectM 3 to VLC, but there are a lot of warnings and compilation issues. We'll get to it, though. |
Excellent, let us know if we can help out! |
I would help if I could, but I don't know how VLC plugins work, and wouldn't know how to interface with system audio if I tried to make a standalone build. If porting the code as a library is a blocker, I could probably help with that. Edit Is the screensaver version not currently working? |
I can contribute, where to start? |
Start with the GLSL branch #26 (soon to be merged to master). I don't know if there is some way to use autotools on windows? I can write up how to build projectM from scratch if that'll be helpful |
Yea please provide build instructions. I will identify/resolve gaps and get the system built on cloud using appveyor.
… On Sep 2, 2018, at 4:38 PM, Mischa Spiegelmock ***@***.***> wrote:
Start with the GLSL branch #26 (soon to be merged to master).
I don't know if there is some way to use autotools on windows?
I can write up how to build projectM from scratch if that'll be helpful
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Is this helpful at all? Let me know if you have any questions or need more details |
Looks good, thanks. I will open new issues as required. |
I managed to get the thing compiled on Cygwin with --enable-sdl. Ended up with the following cyg packages installed (some may not be required):
Also,
Also, set the GL_LIBS variable before configure:
Will provide a PR if this way proves valid. However, upon execution, I get the following output. My knowledge ends here. Does anybody know what may be wrong?
|
Looks like GL is not initialized. Is this the sdl app? Do you have the latest code for it from master? |
It is indeed the SDL application with the latest master. |
Is SDL compiled with openGL support and other required video pieces? |
I'm looking at that now. Dependency Walker shows following dependencies, where CYGSDL2-2-0-0.DLL seems to have no GL deps. Suspicious. c:\tools\cygwin\bin\PROJECTMSDL.EXE:
One way may be compiling SDL from source, but my first try at this generates SDL2.dll, not CYGSDL2.dll as seems to be required. Or trying the MinGW or MSVC way. Tips needed. |
Wish I had some tips to give.. I'm useless with Windows. You can't just use the SDL2.dll provided on the libsdl site? |
I would like to assist. Have you tried msvc?
… On Dec 6, 2018, at 5:25 PM, Mischa Spiegelmock ***@***.***> wrote:
Wish I had some tips to give.. I'm useless with Windows. You can't just use the SDL2.dll provided on the libsdl site?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I have. I'm wondering if there's a way to use the. /configure script to generate vcproj files. Highly doubtful though. Will probably require manually dragndropping libProjectM @ SDL project sources into VS |
I'm in the process of trying to build within MSYS2/MinGW64. All in all, this feels more complete than Cygwin. |
No luck. The SDL included in MSYS is built without OpenGL support. The package build script includes just I decided to build SDL2 myself. The osmesa OpenGL implementation available in MSYS2 seems to be the right way. I compiled SDL2 with Compiling and running projectM-SDL with this however yielded the same result as in Cygwin - I must be doing something terribly wrong. PS I tried debugging and gaining some info on what's actually wrong during execution. Return values of SDL_CreateWindow and SDL_GL_CreateContext were examined (projectM_sdl_main.cpp:94): SDL_Window *win = SDL_CreateWindow("projectM", 0, 0, width, height, SDL_WINDOW_OPENGL | SDL_WINDOW_RESIZABLE);
if (win == nullptr) {
SDL_Log("SDL_CreateWindow failed: %s", SDL_GetError());
}
SDL_GLContext glCtx = SDL_GL_CreateContext(win);
if (glCtx == nullptr) {
SDL_Log("SDL_GL_CreateContext failed: %s", SDL_GetError());
} The log calls were never reached. SDL must be thinking everything's alright in the OpenGL department. |
IMO there are multiple ways ahead regarding Windows:
|
I will try msvc and let you know what I find
… On Jan 5, 2019, at 1:33 PM, Jaroslav Malec ***@***.***> wrote:
IMO there are multiple ways ahead regarding Windows:
Some kernel-level developer needs to step up and make this work (unlikely)
We might try to go the MSVC way. Aside from the apparent need (?) of managing the project files/configuration in Visual Studio in parallel with the ./configure pipeline, there may be hurdles unknown to me.
The emscripten/wasm way might prove to be the way forward.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
the system is barely able to compile on windows (I had to resurrect/modify the old cmake build to regenerate msvc projects and solutions). The SDL2 does not work with my hardware so I cannot test that part, but if I set the fake_audio, it works great! However, the build did require many changes that need preprocessor definitions to prevent breakage of other operating systems. What are the maintenance plans for this project to keep the windows build files in sync with autogen? |
amazing thanks On macos I have an Xcode workspace that was mostly straightforward to set up and keep in sync with things. Don’t know if something similar on Windows is easy or not. Of course a cross platform solution would be nice. Someone is working on seeing if meson would work. Don’t know if it works with windows. |
@mancoast Sweet, mind releasing the changed you made? |
Absolutely! I need to finish the ftgl nuget release to finish the appveyor continuous integration. After the build is on the cloud and verified, I will PR
… On Mar 17, 2019, at 5:48 PM, Jaroslav Malec ***@***.***> wrote:
@mancoast Sweet, mind releasing the changed you made?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Ready to go |
#182 initiated windows x64 continuous integration. @revmischa can you please enable appveyor to build on this repo? then each commit to this repo will automatically generate binary archives for windows. |
Sure, just tell me what to do |
Ok, first step is to sign into appveyor.com using github credentials.
Then you can create a new appveyor “project” for the projectm repo. That’s all! It should automatically read the config settings from the yaml file.
… On Mar 23, 2019, at 4:10 AM, Mischa Spiegelmock ***@***.***> wrote:
Sure, just tell me what to do
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Ok done - not sure if you can view it or not https://ci.appveyor.com/project/revmischa/projectm/builds/23306362/job/6qtay8siv0o0eptx |
Looks great! The windows binary release is under the “artifacts”.
… On Mar 23, 2019, at 12:07 PM, Mischa Spiegelmock ***@***.***> wrote:
Ok done - not sure if you can view it or not https://ci.appveyor.com/project/revmischa/projectm/builds/23306362/job/6qtay8siv0o0eptx
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Great stuff, it works! |
Real input working confirmed:
|
awesome @dzarda want to post a PR with changes/docs? |
Are there any plans to add a Windows binary to the releases, either as a standalone or VLC plugin?
The text was updated successfully, but these errors were encountered: