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

[Disscussion] Port to Windows #11

Open
viktorgino opened this issue Jul 2, 2017 · 8 comments
Open

[Disscussion] Port to Windows #11

viktorgino opened this issue Jul 2, 2017 · 8 comments

Comments

@viktorgino
Copy link
Owner

I had Markus (marlo) reach out to me in email asking about Windows compatibility.

At the moment this isn't something I'd like to focus on, but if there is interest I might reconsider. Also happy to provide some guidance if someone decides to do this.

@stealth-alex
Copy link

It would be good to port project to Windows.

@suhrmann
Copy link
Contributor

suhrmann commented Jul 9, 2017

I think Windows has better IDEs (Visual Studio) for development.
And I think, it's more accessible for many, because install a bleeding-edge Ubuntu (and building the dependecies) is for many not that easy (me included).

Yes, it's a very much work to do, but there are advantages on Win over Linux.

@Vitalic66
Copy link

WIN might be an option, but for many others like me who might use this for a rasp Pi for e.g. car pc project it is importtant to have it Linux based.

It is not easy to manage in Linux but when everything is ready an image for usual users would be enough to make it easy for noob installation.

@suhrmann
Copy link
Contributor

suhrmann commented Jul 9, 2017

The idea of this project was to bring AA to RPi. So basically you're right (besides the RPi 2 supports Windows that is out of the scope currently).

Providing an Image or a container is a good point and might be a simple solution to the difficulties setting this project up.

@viktorgino
Copy link
Owner Author

viktorgino commented Jul 9, 2017

To start with I'd only go with a POSIX compliant Windows compiler (Cygwin or MinGW), because only a minimal set of changes are needed for that (AFAIK only some of the USB code here : headunit-desktop/usbconnectionlistener.cpp and headunit/hu/hu_uti.cpp ).

I managed to get mikereid's headunit running on Windows (without actual video output) a while ago, so
I don't see a reason why wouldn't it work (it can be seen in here: viktorgino/headunit/aa-qt5-test ). Since that I lost interest in going forward with a Windows port, but I believe it is doable.

As for getting started with it on Linux: I'm planning on getting an RPi image and packages (AppImage and/or deb) automatically uploaded by CI, just have to spend a little time with setting it up.

@probonopd
Copy link

Let me know if you need help with the AppImages.

@viktorgino
Copy link
Owner Author

Hey @probonopd ! I've seen your contribution to welle.io and I like the idea of linuxdeployqt, so I will definitely use it. Once I've setup Travis CI I will definitely add automatic generation of AppImages. I will definitely give you a shout when I get stuck with it.
Thanks for the good work!

@ahmadi-ali
Copy link

Hi,
If you give me some more information regarding WINCE version, I am interested to help on developing headunit desktop for WINCE.

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

No branches or pull requests

6 participants