Skip to content
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

compile and then? #27

Open
subabrain opened this issue Aug 3, 2020 · 15 comments
Open

compile and then? #27

subabrain opened this issue Aug 3, 2020 · 15 comments

Comments

@subabrain
Copy link

Hi Friends,

i have a question on how integrate my compiled .xpl librain (example) build.
i dont know where to put the .xpl?

thanks and greets!
Robert

@subabrain
Copy link
Author

hello somebody there?

@dilshaan123
Copy link

Mate , this guy ain’t gonna answers, it’s become a dead town with zombies . He’s gone quite the developer of librain plugin.

@skiselkov
Copy link
Owner

I see your messages, but I simply don't have time to run support for the code. If you don't know how to work with code libraries and the HOWTO and sample code don't do it, I'm afraid there's not much I can do. I don't have the time to teach you basic project structure and coding.

@dilshaan123
Copy link

We are not asking you teach us, all we asking you is make it compatible for Vulkan .Thanks

@kukel
Copy link

kukel commented Aug 11, 2020

@dilshaan123 : You did check this: 9c02c0b

Lots of commits for vulkan back in May. So did you try compiling the code, building a plugin and running it? And report issues so they can be fixed? And noticed it was/is not compatible with vulkan? Since you here request it to be made compatible with Vulkan I assume you tested it. But also state here you are not asking him to teach you but in the commits you are asking how to run this in Vulkan. Sort of contradictory...

@subabrain
Copy link
Author

I see your messages, but I simply don't have time to run support for the code. If you don't know how to work with code libraries and the HOWTO and sample code don't do it, I'm afraid there's not much I can do. I don't have the time to teach you basic project structure and coding.

no problem - your work is good ;)

Greets

@subabrain
Copy link
Author

i just dont know what is need or where i have to put it?
I know in the "plugins" Folder of the aircraft - but what i need further?

Thanks a lot!

Robert

@dilshaan123
Copy link

Mate, thank you so much for your great plugin, got it working for all the aircraft in Vulkan. Keep up your great work .

@dneuge
Copy link

dneuge commented Aug 31, 2020

@dilshaan123 Do you mind sharing how you got it to compile?

I just tried to get it compiled on Ubuntu 20.04 and gave up after about 3 hours. As it seems there is still some work to be done. Using the latest libacfutils master branch (which is currently being worked at - Saso is by far not idle) I had to manipulate librain's qmake.pro to point to the correct glew include directory, so apparently librain currently is not in sync with libacfutils. Just to be sure I replaced libacfutils' copy of the X-Plane SDK with the current one from Laminar; also it appears build_deps and build_redist need to be run on libacfutils (if the build process is documented somewhere then I missed it). To get rid of some errors about API functions not being available I had to add several X-Plane API defines for librain (XPLM302 and XPLM_DEPRECATED). That deprecation notice already screams "this is not ready for release yet" - although it may work for the moment if you can get it compiled. I unfortunately couldn't... I am stuck at cannot find -lacfutils and also glu32.lib and opengl32.lib not being found (32 bit when building 64 bit?!). Maybe that's also caused by libacfutils not having been built correctly; it seems a bit strange that I had to make an undocumented call to qmake -set LIBACFUTILS /path/to/libacfutils for librain to find anything at all.

As I am not that deep into C/C++ build processes I don't think it's worth for me as a simple user to spend any more time on it right now and will just wait for a release unless someone has an idea what I do wrong - I just had to give it a try after the successful reports above but from what I could see so far, it looks like the Vulkan fix is indeed not ready for publication yet.

@kukel
Copy link

kukel commented Sep 2, 2020

@dneuge: After a lot of trial and error I've got something almost compiled and released. Needs some repackaging since not all static libs were linked in it. I'll post a binary in a x-plane.org forum later tonight or tomorrow if it actually works (= some local testing).

Not sure which things helped but I fully compiled/released libacfutils as well and needed newer versions of some source things as well that were in libacfutils to get them compiled on my fedora 32 machine.

@kukel
Copy link

kukel commented Sep 3, 2020

@dneuge: I got it to compile too, fully and it sort of is running. I (think I) needed to make changes mentioned in #20 but then when I tried using it with https://forums.x-plane.org/index.php?/files/file/50106-default-c172-librain-integration/ I did not see anything on my windshield, not in vulkan and not in opengl. When I put librain in 'verbose' logging mode I noticed it did start up and in the FPS/Performance of the plugins I see it is doing 'something'...

@dilshaan123: Did you make the changes mentioned in #20? Or did you make other changes?

@wrb222
Copy link

wrb222 commented Sep 7, 2020

how do did you make it to work in vulkan?

@justnearly
Copy link

hope librain gets vulkan support i probably wont return to xp til it is

@slavsquatter3000
Copy link

can someone send me the .xpl for the librain.plugin thats compatible with vulkan?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants