[Commotion-dev] Non-OpenWRT Directory/Repo Structure

[Hans-Christoph Steiner]

How this stuff is packaged and included is going to vary quite a bit depending
on platform.  For example, on GNU/Linux, servald and commotiond should just be
their own stand-alone native packages (ie. Debian .deb, RedHat .rpm, etc.),
then there can be a 'commotion' package which installs olsrd,
commotion-mesh-panel, servald, etc.

I imagine that Windows and Mac will be similar to each other, in that they
will be something like an app that includes all of the needed binaries.

The actual build process will vary even more, since XCode is what everyone
uses on Mac, Makefiles are the standard GNU/Linux way of building, and Windows
has other common scenarios.  I think forcing each platform into a standard
cross-platform build technique would be a mistake since it would make it
harder for people to get started building and working on the code because
they'd have to learn an unfamiliar project structure.

.hc

On 05/03/2013 12:16 PM, Andrew Reynolds wrote:
> Hans, Bradley, and anyone else working on DR1 feature ports to
> non-OpenWRT platforms,
> 
> Do you have any thoughts on how we should structure Commotion feature
> ports for Linux and Mac? For instance, if we wanted to pull in servald,
> how should we structure the repos and install scripts relative to
> commotion-mesh-applet and commotion-meshbook?
> 
> On the OpenWRT side we define a commotion feed with Makefiles for each
> feature that add and build the correct branches. (See setup.sh in the
> commotion-openwrt repo, which calls
> https://github.com/opentechinstitute/commotion-feed). Can we apply a
> similar model here?
> 
> We kind of touched on this during the developers meeting, but I don't
> think anything was decided in practical terms.
> 
> -andrew
> 
> 
> 
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 939 bytes
Desc: OpenPGP digital signature
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20130503/4a7ed43c/attachment-0001.sig>