RevFE Nightly Builds

I've now got a system set up to upload nightly Windows 32bit builds of the git repository to http://mikesshop.net/revfe-nightly/

These should be uploaded at 1600 eastern time every day, whether there are changes or not. I'm hoping to also work to get an automated changelog, so people can see if there's any reason to download the latest nightly or not.

The system is new, so I'm still working out the kinks. Can't guarantee that it will always be built, or always be available yet, but it's a nice idea.

The link works fine! Keep up the good work. Thanks SNO

where's the .deb files?

MOST linux users are bright enough to figure out how to build it from source.... but if you can't figure it out, I might be able to help you.

Quote:

---

Originally Posted by malcom2073

MOST linux users are bright enough to figure out how to build it from source.... but if you can't figure it out, I might be able to help you.

---

Use the source, Luke?

Can you make nightly builds that publish to a ubuntu ppa? That'd be sweet!

Quote:

---

Originally Posted by tripzero

Use the source, Luke?

Can you make nightly builds that publish to a ubuntu ppa? That'd be sweet!

---

It's GPL, you can :)

So I've been having to manually run the uploader whenever I make changes to the code, since I don't have a reliable way to tell via the git command, what changes have been made.

Does anyone know if there is a version of git diff, that will tell me what's different on the server, rather than what's different on the local copy vs the assumed "master"?

Git fetch would do it, but once that's done once, it can't be done a second time to see the changes again assuming that I don't build once doing that command.

Eg: I can't do git fetch (see changes), then git fetch a second time, since the changes are already fetched.

Sorry for the lack of updates. tripzero has been trying to convince me that a multi-process centric frontend would be more beneficial, so I've been working on trying to code something up. This means that the current codebase of RevFE has been frozen, until I decide if I want to persue this style of frontend, or if I want to revert back to the monolithic style.

I keep forgetting to post updates here. So trip has been successful in convincing me to go multi-process. I've written a working IPC bus daemon and library for communicating between the applications. This means that any app written in any language can communicate with any other application on the bus. This should make "plugin" development much easier. I'm working on a .net library currently for communicating on the bus.

One of the nifty features of this is header generation. This allows an application I wrote to generate a c# .cs file, which you include in your project. This gives you direct native support of events, function calls, etc, as if the other application was embedded inside your own. It's a tough concept to wrap ones head around. I'll hopefully be able to post up some examples showing how to interface with a libobd daemon soon.