At the time I noticed this (maybe 1 year ago), it was not so simple to
get rid of CFLAGS, or perhaps I looked only at opal.
I will take a new look as soon as I find time, thanks.
On 13/04/14 22:16, John Smith wrote:
Hrm.
ptlib's configure seems to modify CFLAGS like this:
CFLAGS="-g -O2"
ov
Hi,
I checked out the sources for ptlib as described here:
http://wiki.ekiga.org/index.php/Download_Ekiga_sources
But when I './configure --prefix=/usr && make', I get this build error:
[CC] ptclib/inetprot.cxx
[CC] ptlib/common/notifier_ext.cxx
[CC] ptclib/vcard.cxx
[CC] ptclib/guid.cxx
make[2
On 14/04/14 09:38, John Smith wrote:
Hi,
I checked out the sources for ptlib as described here:
http://wiki.ekiga.org/index.php/Download_Ekiga_sources
But when I './configure --prefix=/usr && make', I get this build error:
[CC] ptclib/inetprot.cxx
[CC] ptlib/common/notifier_ext.cxx
[CC] ptcli
On 14/04/14 10:02, Eugen Dedu wrote:
On 14/04/14 09:38, John Smith wrote:
Hi,
I checked out the sources for ptlib as described here:
http://wiki.ekiga.org/index.php/Download_Ekiga_sources
But when I './configure --prefix=/usr && make', I get this build error:
[CC] ptclib/inetprot.cxx
[CC] pt
On Mon, Apr 14, 2014 at 10:11 AM, Eugen Dedu
wrote:
> On 14/04/14 10:02, Eugen Dedu wrote:
>>
>>
>> I thought I fixed this. What version of ptlib do you compile?
>
>
> Err, sorry, I fixed it in the repository, but no release has been done
> afterwards...
>
> Please use the branch v2_10 of ptlib,
On 14/04/14 10:38, John Smith wrote:
On Mon, Apr 14, 2014 at 10:11 AM, Eugen Dedu
wrote:
On 14/04/14 10:02, Eugen Dedu wrote:
I thought I fixed this. What version of ptlib do you compile?
Err, sorry, I fixed it in the repository, but no release has been done
afterwards...
Please use the
On Mon, Apr 14, 2014 at 10:56 AM, Eugen Dedu
wrote:
>
> If you used the line above (svn export...), then you have already the good
> source code. So the error is elsewhere, and I was wrong about it.
>
> Don't you have the file ./src/ptlib/common/getdate.tab.c in ptlib directory?
> What is the com
On 14/04/14 11:01, John Smith wrote:
On Mon, Apr 14, 2014 at 10:56 AM, Eugen Dedu
wrote:
If you used the line above (svn export...), then you have already the good
source code. So the error is elsewhere, and I was wrong about it.
Don't you have the file ./src/ptlib/common/getdate.tab.c in pt
Hi,
I am getting an error [1] building opal.
Regards,
John Smith
[1]
h263-1998.cxx:97:58: note: candidates are:
In file included from h263-1998.cxx:58:0:
../common/dyna.h:88:7: note: FFMPEGLibrary::FFMPEGLibrary()
class FFMPEGLibrary
^
../common/dyna.h:88:7: note: candidate expec
On Mon, Apr 14, 2014 at 12:37 PM, Eugen Dedu
wrote:
>
> Ok, so you do not use the latest code from the branch, but the release, that
> is the reason of the error.
>
> Remove your ptlib directory, and use:
>
> svn export
> https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/branches/v2_10
>
On 14/04/14 15:16, John Smith wrote:
Hi,
I am getting an error [1] building opal.
Regards,
John Smith
[1]
h263-1998.cxx:97:58: note: candidates are:
In file included from h263-1998.cxx:58:0:
../common/dyna.h:88:7: note: FFMPEGLibrary::FFMPEGLibrary()
class FFMPEGLibrary
^
../co
On Mon, Apr 14, 2014 at 3:23 PM, Eugen Dedu
wrote:
>
> Do you use libav or ffmpeg? Which version?
>
> Do you need H263 and H264 video codecs or not? If not, it is simpler.
>
Im using ffmpeg 2.1.4. Im trying to build for as much support of
anything as possible.
I have these packages installed:
On 14/04/14 15:30, John Smith wrote:
On Mon, Apr 14, 2014 at 3:23 PM, Eugen Dedu
wrote:
Do you use libav or ffmpeg? Which version?
Do you need H263 and H264 video codecs or not? If not, it is simpler.
Im using ffmpeg 2.1.4. Im trying to build for as much support of
anything as possible.
On Mon, Apr 14, 2014 at 3:35 PM, Eugen Dedu
wrote:
>
> I always test with libav. It seems that supporting libav and ffmpeg is a
> real mess.
>
> Please recompile opal with --disable-libavcodec to disable ffmpeg
> involvement. When everything goes well we can tackle this issue too.
>
It builds wh
On 14/04/14 15:47, John Smith wrote:
On Mon, Apr 14, 2014 at 3:35 PM, Eugen Dedu
wrote:
I always test with libav. It seems that supporting libav and ffmpeg is a
real mess.
Please recompile opal with --disable-libavcodec to disable ffmpeg
involvement. When everything goes well we can tackle
Hi,
Just for fun, I decided to run the llvm/clang static source code
analyzer on ptlib, opal, and ekiga.
The results can be found here:
ptlib
http://lbalbalba.url.ph/clang/ptlib/
opal
http://lbalbalba.url.ph/clang/opal/
ekiga
http://lbalbalba.url.ph/clang/ekiga/
Regards,
John Smith
Hi,
Le 14/04/2014 18:24, John Smith a écrit :
Hi,
Just for fun, I decided to run the llvm/clang static source code
analyzer on ptlib, opal, and ekiga.
The results can be found here:
ptlib
http://lbalbalba.url.ph/clang/ptlib/
opal
http://lbalbalba.url.ph/clang/opal/
ekiga
http://lbalbalba.
On 14/04/14 20:27, Julien Puydt wrote:
Hi,
Le 14/04/2014 18:24, John Smith a écrit :
Hi,
Just for fun, I decided to run the llvm/clang static source code
analyzer on ptlib, opal, and ekiga.
The results can be found here:
ptlib
http://lbalbalba.url.ph/clang/ptlib/
opal
http://lbalbalba.url
On Mon, Apr 14, 2014 at 8:27 PM, Julien Puydt wrote:
>
> I pushed a commit to fix those in ekiga... I'm actually quite surprised
> there was so little to complain about!
>
Cool. 'cppcheck' hasnt got much more to complain about either:
http://lbalbalba.url.ph/cppcheck/ekiga/
Regards,
John Smith
On Mon, Apr 14, 2014 at 9:05 PM, Eugen Dedu
wrote:
>
> ptlib and opal are too old to bother with those issues. We are working to
> use the newest ptlib/opal code...
>
I can checkout the latest revisions of ptlib/opal and run the analyzer on that.
Regards,
John Smith.
_
On 14/04/14 21:08, John Smith wrote:
On Mon, Apr 14, 2014 at 9:05 PM, Eugen Dedu
wrote:
ptlib and opal are too old to bother with those issues. We are working to
use the newest ptlib/opal code...
I can checkout the latest revisions of ptlib/opal and run the analyzer on that.
Good, please
On 4/14/14, 12:13 PM, Eugen Dedu wrote:
On 14/04/14 21:08, John Smith wrote:
On Mon, Apr 14, 2014 at 9:05 PM, Eugen Dedu
wrote:
ptlib and opal are too old to bother with those issues. We are
working to
use the newest ptlib/opal code...
I can checkout the latest revisions of ptlib/opal and
On Mon, Apr 14, 2014 at 9:23 PM, Craig Southeren
wrote:
> On 4/14/14, 12:13 PM, Eugen Dedu wrote:
>>
>> On 14/04/14 21:08, John Smith wrote:
>>>
>>> On Mon, Apr 14, 2014 at 9:05 PM, Eugen Dedu
>>> wrote:
ptlib and opal are too old to bother with those issues. We are working
t
Le 14/04/2014 21:06, John Smith a écrit :
On Mon, Apr 14, 2014 at 8:27 PM, Julien Puydt wrote:
I pushed a commit to fix those in ekiga... I'm actually quite surprised
there was so little to complain about!
Cool. 'cppcheck' hasnt got much more to complain about either:
http://lbalbalba.url.
On Mon, Apr 14, 2014 at 9:48 PM, Julien Puydt wrote:
>
> I fixed them too, but I'm quite unhappy: the default C++ constructors were
> adequately taking care of things, so those weren't worth it. In fact, to get
> more correct core, one should probably *remove* the lines I added, and then
> some mo
25 matches
Mail list logo
