On 8/28/07, Ray Jackson [EMAIL PROTECTED] wrote:
Hi all,
Okay, I managed to iron out the build problems with MinGW and Wengo and
reached the Linking stage for the WengoPhone.exe. Now I have come up
against the 'input line is too long' problem on the Windows cmd line. I
have heard reference
Hi Ray,
Ray Jackson wrote:
Okay, I managed to iron out the build problems with MinGW and Wengo and
reached the Linking stage for the WengoPhone.exe. Now I have come up
against the 'input line is too long' problem on the Windows cmd line. I
have heard reference to Perl/Python scripts, Scons
Thanks for the info. I did manage to get a fair way with MinGW - seems
that I couldn't quite finish the job off at the linking stage at the end
:( I always like to try and use open source/free (as in speech)
software first, but I may have to succumb to the beast this time and use
VC++ :)
Hi Ray,
Ray Jackson wrote:
Can I just say what a superb job you guys are doing with the 2.2
release! I am running it against our SIP platforms here and it is
working great so far!
Thank you! What SIP platforms are you using?
By the way, is there any documentation on the sign-in procedures
Dave Neary wrote:
Hi Ray,
Ray Jackson wrote:
Can I just say what a superb job you guys are doing with the 2.2
release! I am running it against our SIP platforms here and it is
working great so far!
Thank you! What SIP platforms are you using?
A combination of open source
Hi all,
Okay, I managed to iron out the build problems with MinGW and Wengo and
reached the Linking stage for the WengoPhone.exe. Now I have come up
against the 'input line is too long' problem on the Windows cmd line. I
have heard reference to Perl/Python scripts, Scons etc. but can't find
