-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Linux/Macos port #31
Comments
yes please that would be great to have a guid for linux or even compiled binaries! |
I still have hope to find a contributor for the Mac/Linux port :) |
Amazing Project @CedricGuillemet I have just started playing with building in a ubuntu:18.04 docker container. Which version of Ubuntu did you use to compile against? I would be happy to follow through with build bot if you can share some build specifics with me. (note: I am not the greatest C++ person) |
Hi |
So I am back. https://dev.azure.com/highway900/Imogen/_build/results?buildId=4 That is the build result with a fairly vanilla cut of master. The only change is setting the C++ standard to 17. This fixed numerous build errors like using auto. The current errors can be fixed by including I can invite you to the azure project, or you could start one for the project. I just thought it might be an easy way to run the builds and create some release/build artifacts for many platforms automatically. Cheers. |
That looks nice! Is there a way to not create a repo on azure but use github instead? |
The azure build system just points at my github fork of Imogen :) So there is no azure repository that I know of. I did allow access to azure to my fork. |
As far as I can tell the version of I will try to compile with the linux python3.7-dev package instead. |
Compiling with an installed version of python3.7 and package lookup in CMakeLists fixed the python dependency. Now the compiler semantics are appearing. I get a different set of errors for GCC and Clang. I will focus on Clang at the moment in the hope that translates to OSX easier. Changing the C++ standard (11, 14, 17) also generates a variety of different errors. I am currently using 14 as 17 causes errors with pybind, which fits VS the best? |
I don't know. I use vs2017 default settings. Focusing on Clang is a good idea. |
I just tried to build current "dev-0.14" branch and got this error: |
The path for SDL is likely incorrect in the include.
‘#include <SDL/SDL.h>’
This is actually where ‘SDL.h’ is. I would suggest changing the cmakelists
file to search in the include subdirectory.
…On Sun, 2 Jun 2019 at 04:34, axredneck ***@***.***> wrote:
I just tried to build current "dev-0.14" branch and got this error:
/home/redneck/programs/Imogen/src/EvaluationContext.cpp:26:10: fatal
error: SDL.h: No such file or directory
#include <SDL.h>
though i have this file (/usr/include/SDL/SDL.h).
Arch Linux.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#31?email_source=notifications&email_token=AAIMTYGBIWIWDAXD3BG5GNTPYK6KVA5CNFSM4GGGTT4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXGFSY#issuecomment-497967819>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIMTYB2BFZ5WJ33IRTMT73PYK6KVANCNFSM4GGGTT4A>
.
|
Trying to compile dev-0.14 branch: |
What's your compiler/OS? The platform.h sets the configuration and enables features based on the target. Currently, only Windows thru MSVC and emscripten are supported. |
@CedricGuillemet Arch Linux as before, GCC 8.3.0 |
Hey! Are you looking for help with the Linux port? I'm no developer but I could help with testing. I'm a graphic designer and I'm really excited to see Imogen being a thing, as I want to make procedural PBR materials, but I don't want to become Adobe's servant for this. I'd be really excited to help you develop the Linux port of Imogen (the web build doens't seem to work well for me). I'm running Ryzen 7 1700 / GTX 1060 6GB / 32GB RAM and Manjaro Linux. |
I've truied building the newest git code on Linux, as well as the latest release. No success so far. Building the latest release I get this error:
|
I think I have the same issue: |
Yes, I broke the linux build with emscripten. Fixing it now. |
Any plans for appimage releases? |
@nafergo any plans for compile from sources first, the rest later. |
Now it compiles but crashes:
|
It crashes because it doesn't find the font file. In your terminal run the app from the bin directory |
Thank You, it works! |
Doesn't compile again
Arch Linux, Imogen dev-0.14 branch. |
Try updating the submodules. |
Already tried with no success. |
Apparently, something is broken with bgfx, because I updated the submodules and now is failing for me also. |
The error I'm getting is because of this change in bgfx |
I'm not sure (I didn't read all the imogen code) but maybe will be healthier to use Vulkan directly, cause bgfx is doing api changes. You can use vukan on linux and windows and MolteVk or similar on macos. |
I can't reproduce the issue with cmakegui + msvc :( |
It happens if you update the submodules recursively cause they are making changes on bgfx, check |
Can be fixed just by replacing |
But then I started to get more bgfx errors, updating the submodules was a bad idea. |
I've pushed an update. let if know if it solves something |
I did
|
Everything is coded with multiplatform in mind (mostly). And I compiled the project on a virtualized Ubuntu. It was a couple months ago and a Linux port (a solid one) would be great.
Kudos if there is a possibility to produce binaries(packages) from a bot.
The text was updated successfully, but these errors were encountered: