[reSIProcate] git
Scott Godin
sgodin at sipspectrum.com
Wed Dec 5 08:03:17 CST 2012
I'd second Adam's point. Any resip cycles we might have should be spent on
what Adam has outlined below first.
Also - here's some text from an old email I sent on the subject:
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 at nostrum.com> 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 at resiprocate.**org <resiprocate-devel at resiprocate.org>
> https://list.resiprocate.org/**mailman/listinfo/resiprocate-**devel<https://list.resiprocate.org/mailman/listinfo/resiprocate-devel>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20121205/b61bb6c0/attachment.htm>
More information about the resiprocate-devel
mailing list