Search results

It is in working condition - vcpkg packages work correctly without additional input if vcpkg is installed and CMakePresets.json is used (or vcpkg toolchain is specified, if ignoring CMakePresets) However, if the developers don't want to use new tools, then it's obvious there is no place for new...

How about we solve it going forward then? We have definite code "owners" for some areas - e.g. Jarmonik for D3D9Client, dbeachy for XRSound, myself for CMake magic and/or GH actions stuff - how about we add a CODEOWNERS file to the repo so that specific people are called in to review...

What were the build problems you experienced? Every commit in main is built using CI - so if the code didn't compile for you, CI should be improved it so it better reflects local environment. Happy to take a look Yes, that is the question posed in the original post. Should we "go fast and break...

VCPKG component needs to be explicitly installed in Visual Studio. You can install it manually using Visual Studio installer or just import the vsconfig file into it - and it will install all missing components P.S. It also works from command line: VisualStudioSetup.exe --config...

Hello Orbiter community, We're at a crossroads regarding Orbiter's Lua language support implementation, and would like to get community input on the best way to proceed. There is an ongoing push to modernise Orbiter codebase, namely: To remove support for obsolete platforms (x86, DX7) To...

Please note that what I'm suggesting isn't "git-flow", but a model which combines "mainline" development - where features are merged into main - with branches cut off for specific releases. This allows both to patch old releases if necessary, and maintain tempo of development in main In the...

This works well in following cases: You have comprehensive test coverage which gives you close to 100% confidence nothing is broken You can rollback releases really rapidly - e.g. just redeploy from previous commit You have low cost of error - e.g. a button of wrong color is not a show-stopper...

Would like to propose this as a starting point to discuss roadmap: https://www.orbiter-forum.com/threads/roadmap-proposal-orbiter-development.40423/

Hi, Given the positive reception proposals outlined in Council thread, I think we may be able to move forward and start outlining possible future directions in Orbiter development. Below text first and foremost describes my personal vision of how the project may progress - but I am hoping that...

Greetings Given that @martins - most understandably - may not have time to dedicate to constant development of Orbiter, I think it might be worth discussing whether and how the community itself may help the project to progress. I think everyone would agree that having a single person be a gate...

I don't experience that, what is the error message? For .cfg files - I guess the correct way to solve it would be to have a customized "install" command for CMake which mimics "copy if newer" Visual Studio behavior. I know it is possible in theory, will need to dedicate some time to implement

Yes, that is correct. In make/CMake terms the "build" directory is a temporary scratchpad and the "install" is the one with final product (although personally I would still install into separate dir to be in the safe side). The target model withCMake is that you have source dirs in safety and...

Sorry to hear that - did you have build dir in your Orbiter directory, however? That has potential for failure regardless of whether you use Visual Studio or command line. If you need a "merged" install, at the very least it should be "install" dir which is pointing to an active installation...

XRSound is part of Orbiter repository already - you need to download irrKlang SDK for it separately because of licensing issues (@dbeachy1 can probably comment on it more) D3D9Client will be integrated soon™ - there's a WIP branch to merge it

You can adjust build and "install" directory to your liking in your CMakeSettings. Not entirely clear what do you mean by "keeping installation up to date" - you mean updating the repository? This can be done either by "git pull" command, or by using Git Changes window in Visual Studio - it has...

Hi, Seeing a lot of questions pertaining to how to develop Orbiter using Visual Studio 2019, I've decided to share the setup I use Steps: 1.Install latest version of Visual Studio 2019 Required components: "Desktop Development with C++" package "MFC for latest build tools" component under...

Checkout this branch: https://github.com/DarkWanderer/orbiter/tree/linux Then: mkdir -p out/build cd out/build cmake -G Ninja ../.. -DCMAKE_CXX_COMPILER=/usr/bin/wineg++ cmake --build . -- -k0 There's a ton of errors at the moment, of course, due to non-POSIX functions being used in some...

GitHub orbiter installation does not have textures. Do you have Orbiter 2016 installation on your machine? You need to set ORBITER_PLANET_TEXTURE_INSTALL_DIR variable for CMake when configuring so that your freshly-built Orbiter version can correctly init graphics

winegcc/wineg++ does exactly that if I'm not mistaken?

Out of curiosity, why would this method require non-const operations in your use case? From the signature, it should only change state of objects passed to it (no critique, trying to understand the reasons)