how to compile pcp or any new application using libjingle api

[Google Code Exporter]

What steps will reproduce the problem?
1. Downloaded and installed libjingle 0.6.13 on Fedora 14 64 bit.
2. Ran into various path / scons related issues but found help here and got 
those fixed.
3. I can run call application, but in my debug mode build, there is no pcp 
binary generated. How do i build pcp? And secondly, how do i build a new 
application that i create once i get to use api's of any of existing ones.

What is the expected output? What do you see instead?

talk/build/dbg/staging should have contained pcp too. Instead it contains call, 
login, stun server and client binaries.

What version of the product are you using? On what operating system?
0.6.13 on Fedora 14 64 bit

Please provide any additional information below.

Original issue reported on code.google.com by [e-mail] on 11 Mar 2012 at 11:06

[Google Code Exporter]

pcp was excluded long time ago and would be updated in low priority.

If you really want to build it, you could do as following.
1. in case of latest version, at last of libjingle.scons you could add build 
instructions.
2. You can use old version that pcp is included in scon file. (e,g,. libjingle 
0.4.0.)

Original comment by [e-mail] on 14 Mar 2012 at 1:47

[Google Code Exporter]

Hi Adam,

Thank you for your feedback.

1. Does PCP being excluded means that it won't work well even if i get to build 
it successfully?
2. How can i add a new separate application to the build process? Same towards 
end of libjingle.scons? Is there a sample or guideline?

Thanks,
Fayyaz

Original comment by [e-mail] on 14 Mar 2012 at 10:12

[Google Code Exporter]

Issue 373 has been merged into this issue.

Original comment by [e-mail] on 1 Jun 2013 at 4:58

[Google Code Exporter]

Issue 334 has been merged into this issue.

Original comment by [e-mail] on 1 Jun 2013 at 4:59

[Google Code Exporter]

Issue 337 has been merged into this issue.

Original comment by [e-mail] on 1 Jun 2013 at 5:00

[Google Code Exporter]

Issue 383 has been merged into this issue.

Original comment by [e-mail] on 1 Jun 2013 at 5:01