I prefered coding in Ubuntu, i have been understanding the structure of haiku for couple of days. I got interest in the testing project.
I Found this article by andrew Lindesay - Haiku Development from Linux
it requires synching code.
Is there any recommended workflow for ubuntu users?
As a newcomer to Haiku, I’d like to recommend Genio as IDE.
Currently I’m in a similar boat; I’m developing a command-line tool, which I currently write most of under Debian. When I transfer the sources to Haiku and build there, I’ve had several things to fix. Most of the incompatibilities I’ve had are network related).
You’ll quickly notice that the settings you’re used to have in your ~/, ~/.local or~/.config directory have moved into config/settings/ (including .bashrc and .profile, which are now named bashrc and profile)
Also /usr/includes/ are found in /system/developer/headers/ instead.
I can’t cover everything, but those are some of the first things I noticed were different.
1 Like
Currently I have the source code insdie the haiku, and i am writing from Ubuntu.
I used sshfs to mount the Haiku source code directly into Ubuntu, and I open that in VS Code. used ssh to access haiku terminal for build commands,
though to run some files with UI needed, I run them from haiku.
I tried Genio, Currently i am not used to it.
The environment is complex then to code itself. It took me so much time either. Or maybe i am missing any convinient environment.
What are you trying to develop? If it’s kernel code for example, using the vm way can work fine. Though note there is no reason why you have to compile the code in Haiku, you can do it from ubuntu and then open a new virtual machine with your tested changes (for this kind of on-off booting qemu is much easier to use though)
If you want to develop applications on Haiku it may be best to set up a dual boot with Haiku
1 Like
@nephele, right now i am working on serialconnect
I am interested in the Unit testing Gsoc project and finding a way to make the testing “Rule rather than exception“,
Why such messy setup?
the issue with testing part is, in regular build, jam does not inject those test builds in iso, it has to be done with buildconfig,
I picked that environmnet so i dont need to reboot the iso, just two tabs and working on, one with writing and building and next is for like running the files in haiku.
Improve automated test coverage:
could you identify main areas to focus for unit testing.
some are using Fixture (in support, string tests) and some using other standard cppunit format (in coding guildelines) for making suites.
shortly code structure is not consistent.
I am thiking to focus on key areas to make them realible and a setup so that
- contributor easily write the code, with .
- they make sure they are not violating any error,