Re: H323plus and ptlib 64 bits

Re: H323plus and ptlib 64 bits

Jess

Just use PTLIB Static and statically link PTLIB with h323plus (ie link 
to ptlibs.lib)

If using PTLIB v2.10.x
In include/ptbuildopts.h.in at around line 190
#if defined(P_OSSL) && !defined(_WIN32_WCE) && !defined(_WIN64)

Do a rebuild.

Simon

On Wed, 1 Feb 2012 11:53:03 +0800, Y030052 Ng wrote:
> Hi Simon,
>
> In which file exactly should I place #undef P_SSL?
>
> I am able to compile "configure" and "PTLib Static" and "MergeSym"
> projects in x64, but stuck in compiling "PTLib DLL" project. The 
> build
> output is below.
>
> By comparing the build output for win32, it seems that the problem is
> in creating ptlib.lib. But I have no idea how to fix this. Please
> helps. Thank you.
>
> 1>------ Build started: Project: PTLib DLL, Configuration: Release 
> x64
> ------
> 1>Build started 1/2/2012 11:44:35 AM.
> 1>InitializeBuildStatus:
> 1> Touching "......LibReleasePTLib DLL.unsuccessfulbuild".
> 1>C:Program Files
> (x86)MSBuildMicrosoft.Cppv4.0Microsoft.CppCommon.targets(151,5):
> warning MSB8015: Forcing a rebuild of all source files due to the
> contents of "D:H323plusptlib64LibReleasecustombuild.command.1.tlog"
> being invalid.
> 1> Merging symbols ...
> 1> MergeSym version 1.7.0 on Windows 7 by Equivalence
> 1>
> 1> Symbols merged: 11975 added, 15728 removed.
> 1>C:Program Files
> (x86)MSBuildMicrosoft.Cppv4.0Microsoft.CppCommon.targets(151,5):
> warning MSB8015: Forcing a rebuild of all source files due to the
> contents of "D:H323plusptlib64LibReleasecustombuild.command.1.tlog"
> being invalid.
> 1>ClCompile:
> 1> dllmain.cxx
> 1>ptlib.def : error LNK2001: unresolved external symbol =
> 1>......Libptlib.lib : fatal error LNK1120: 1 unresolved externals
> 1>
> 1>Build FAILED.
> 1>
> 1>Time Elapsed 00:00:15.96
> ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
> ==========
>
> Jess
>
> -------------------------
> From: s.horne <at> packetizer.com
> To: y030052 <at> live.com; h323plus <at> lists.packetizer.com
> Subject: RE: [h323plus] H323plus and ptlib 64 bits
> Date: Wed, 1 Feb 2012 02:18:55 +1000
>
> Jess
>
> I just checked in CVS x64 definitions for the vs2010 project file.
>
> For PTLIB 2.10.x create the x64 project based on win32 project and
> #undef P_SSL (they point to win32 OpenSSL)
>
> It should compile (you will have a few warnings)
>
> Simon
>
> FROM: h323plus-bounces <at> lists.packetizer.com
> [mailto:h323plus-bounces <at> lists.packetizer.com] ON BEHALF OF Y030052 
> Ng
> SENT: 31 January 2012 15:47
> TO: h323plus <at> lists.packetizer.com
> SUBJECT: [h323plus] H323plus and ptlib 64 bits
>
> Hello,
>
> Is it possible to compile H323plus and Ptlib in 64 bits under Windows
> 7 and Visual Studio 2010? Can someone guide me on this? Thank you.
>
> Best regards,
>
> Jess

Re: H323plus and ptlib 64 bits

Unable to load H.263 and H.264 plugin dll for x64 windows

Re: Unable to load H.263 and H.264 plugin dll for x64 windows

Re: Unable to load H.263 and H.264 plugin dll for x64 windows

Re: Unable to load H.263 and H.264 plugin dll for x64 windows

Minor issues with upnp

Re: Minor issues with upnp

Hi,

the GetPeerAddress() issues should already be fixed in the latest CVS.

Regards,
Jan

J.C Mercier wrote:
> Hi all,
> 
> If i may first note, I've compiled the latest h323plus with no problem, but
> when i go to compile the simpleplus program, it gives an unresolved error
> for H46019UDPSocket::GetPeerAddress(...).   This happens because
> H323_H46024A and H323_H46024B are disabled and GetPeerAddress is defined
> within H323_H46024A but declared within H323_H46019M. I did a minor work
> around and it now compiles fine.
> 
> Another issue I came upon, when I initialize UPNP during the h323
> initialization, during the UPnPThread::TestMapping()  function call, it
> manages to map both ports (11000 and 11001) but after calling
> RemoveMap(extPort,true);  and  RemoveMap(extPort+1,true), only 11001 is
> removed and not 11000. I tested this with different port range and it
> produces the same results (one unmapped and not the other). Is this
> supposed to be the case or is something wrong somewhere?
> 
> Although, after closing the program, both ports are unmapped successfully.
> But another problem that happens every time I close the program is a memory
> access violation at;
> 
>     ~IxNATNumberOfEntriesCallback() { delete m_pointer; } from
> 
> interface IxNATNumberOfEntriesCallback : public INATNumberOfEntriesCallback
> 
> Any reason why this could be the case?
> 
> Lastly, when upnp is initialized, making a call doesn't seem to open and
> map the ports at all. What else should be done aside from initializing
> upnp?
> 
> Your help and suggestions will be greatly appreciated.
> 
> Thanks
> 
> Josh

--

-- 
Jan Willamowius, jan <at> willamowius.de, http://www.gnugk.org/

Re: Minor issues with upnp