Shared repository?

I no longer run servers at home - I'm doing the builds on my desktop. I did set up jenkins and get it to do some builds, but never converted to it. I'm using a shell script to do them.

I have a ubuntu 10.4 VM I used to use for builds, and doing an occasional build that way is ok. But doing development on it is a real pain. So I ported the build system to my desktop.

The Makefiles have a number of non-portable assumptions built into them. I got the easy ones out, but I'm not sure they can all be eliminated for both ARM & desktop builds, so dealt with some of them by creating an environment for deviation builds that is unusable for most other software. This also involved switching to GCC 5.0, whose new warnings turned up some interesting bugs.

I managed to get the windows binaries to build and execute, but they always come on in USB mode for some reason.

Any chance you can start a second set of nightlies from the team repository? Not only would that fix the issue with providing windows binaries, but it would also get the distribution off of Google Drive, which was temporary hack until you decided what was going to be done with this repository.

USB mode at startup occurs when current directory is different from that of executable.

Ok, I now have the windows emulators building.

I'm leery of pushing this because I suspect that it will break your Windows builds. Mostly, it's that the mingw32 compiler I'm using doesn't recognize the -mno-cygwin flag. I suspect this is why the binaries complain about missing dll's unless I build with static libgcc and libstdc++.

I also don't have - and don't see any clue as to how to build - libportaudio-2.dll. The binaries run without it, but sound may not be working properly.

I've added you as a reviewer for the pull request so you can check it yourself.

The downloads section now has a newer build than the Google drive version, so I've turned off the nightly build that was going to Google drive, and nuked the google drive folder.

There's no way to attach a message pointing back to the downloads section (google drive doesn't work well for this), but anyone who was keeping close enough tabs to be watching it should also know to check the new downloads section as well.

Some of the issues have been fixed in the team repository. For instance, 578 .

Do you have preferences for how these should be handled?

Hi PB welcome back

I'm anxiously looking forward to the next release, gonna try and help with whatever I can.

Edit: going to try a merge with my repo, waiting for a nightmare to happen lol

Hi,
I would like to join to work in DEVO12S gui if allowed.

People are no longer doing direct commits to the team repository, except for PB. Even if we have a commit bit, we're generating pull requests from our clones.

So that's the approach to take now. Clone the team repository, create branches for your features, as working on the default branch will require a clone for each feature. Then add pull requests for them to the team repository.

Hi mwm,

I always thought that shared repository was better for small teams.

At the moment i have here my repo bitbucket.org/lyndros/deviation-lyndros-bugfixing is a clone of the bitbucket.org/PhracturedBlue/deviation .

Is that still the official repo for developers?

Cheers

No. All work / commits for nightly-build to the default/trunk went to:

bitbucket.org/deviationTX/deviation