reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] git

> - slightly under half of what you request is explained in the configure
help text, e.g.

All of what I mentioned is presented to the user via simple Yes/No and path based questions that are prompted to you interactively via the old configure scripts (without command line options).  This made things dead simple for users.

Scott

On Wed, Dec 5, 2012 at 9:54 AM, Daniel Pocock <daniel@xxxxxxxxxxxxx> wrote:



On 05/12/12 15:03, Scott Godin wrote:
> I'd second Adam's point.  Any resip cycles we might have should be spent on
> what Adam has outlined below first.

The real benefit with git is that it supports bringing more contributors
to reSIProcate, which in turn means the net number of cycles spent on
reSIProcate goes up.  I don't see it primarily as something for my own
convenience (as I can already work privately with git-svn tracking the
SVN repo), but as an initiative for community building.


> Also - here's some text from an old email I sent on the subject:



I don't have time to fully document this now, but I would just observe that:

- slightly under half of what you request is explained in the configure
help text, e.g.

     ./configure --help

- and some other things (cross compiling) should work the normal
autotools way (i.e. any standard autotools guide explains these things,
and there is nothing special I have done for it with reSIProcate), e.g.

     ./configure CC="/opt/toolchain/for/cross/compile/cc"

My first effort to answer this more fully is likely to involve giving
links to the autotools manual pages and/or some useful examples, but
people with really specific needs can find the best support through the
autotools community and the mailing lists (where questions do get
answered quite quickly)





> We should have some form of help text, that enables someone to migrate to
> the new build system as painlessly as possible.  In order to do this,
> people must understand how to do the things they used to do with the old
> ./configure script.  This includes:
>
> 1.  An example of how to switch tool chains / cross compile.
> 2.  An example of how to switch from debug builds to opt builds.
> 3.  How to build shared libraries vs show to build static libraries.
> 4.  How to use DISTCC
> 5.  How to use CCACHE
> 6.  How to build MySQL support into repro
> 7.  How to build dum with radius client support
> 8.  How to build tfm
> 9.  How to build recon
> 10. How to build reTurn server
> 11.  How to build reTurn client
> 12.  How to build with or without OpenSSL
> 13.  How to build with or without DTLS support
> 14.  How to build with CURL
> 15.  How to build with Google Malloc
> 16.  How to build with Google CPUPerf
> 17.  How to build with Debug Malloc
> 18.  How to build with Electric Fence
> 19.  How to build with Random Thread Local option enabled
> 20.  How to build with IPv6 enabled
> 21.  How to build with EPoll support
> 22.  How to build with POPT support
> 23.  How to build with Fixed Point only option enabled
> 24.  How to build with Pedantic Stack option
> 25.  How to build with Dum Thread Debug on
> 26.  How to build with CARES
>
> All these options are from the old configure script.  I know you've covered
> some of these with your examples, but it would be great to cover them all
> in some fashion.
>
> Scott
>
> On Mon, Dec 3, 2012 at 10:26 AM, Adam Roach <adam@xxxxxxxxxxx> wrote:
>
>> On 11/19/12 03:20, Daniel Pocock wrote:
>>
>>> I'm just going to revive the git discussion now that we are over the
>>> autotools hurdle
>>>
>> Can we finalize the autotools stuff before moving on to the next big thing?
>>
>> For example, this needs a complete rewrite, letting people know how to do
>> all the things it says how to do, but with the new build system:
>>
>> https://svn.resiprocate.org/**rep/resiprocate/main/README<https://svn.resiprocate.org/rep/resiprocate/main/README>
>>
>> The following wiki pages need to also be updated to be correct:
>>
>> http://www.resiprocate.org/**Quick_Subversion_Checkout_and_**
>> Compilation_HOWTO<http://www.resiprocate.org/Quick_Subversion_Checkout_and_Compilation_HOWTO>
>> http://www.resiprocate.org/**The_reSIProcate_build_system<http://www.resiprocate.org/The_reSIProcate_build_system>
>> http://www.resiprocate.org/**AutotoolsBuild<http://www.resiprocate.org/AutotoolsBuild>
>> http://www.resiprocate.org/**AutotoolsMigration<http://www.resiprocate.org/AutotoolsMigration>
>> http://www.resiprocate.org/**Configuration_Options<http://www.resiprocate.org/Configuration_Options>
>> http://www.resiprocate.org/**Using_Repro#Installing_on_**
>> Linux_OS_or_Unix-Like_Systems<http://www.resiprocate.org/Using_Repro#Installing_on_Linux_OS_or_Unix-Like_Systems>
>> http://www.resiprocate.org/**Building_recon#Building_recon_**
>> on_Generic_Linux<http://www.resiprocate.org/Building_recon#Building_recon_on_Generic_Linux>
>>
>> There might be a few places I've missed, but I think those are the
>> important ones.
>>
>> /a
>> ______________________________**_________________
>> resiprocate-devel mailing list
>> resiprocate-devel@resiprocate.**org <resiprocate-devel@xxxxxxxxxxxxxxx>
>> https://list.resiprocate.org/**mailman/listinfo/resiprocate-**devel<https://list.resiprocate.org/mailman/listinfo/resiprocate-devel>
>>
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel