Menu
▾
▴
iaxclient-devel — Development Discussion List
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(3) |
Mar
(16) |
Apr
(11) |
May
(3) |
Jun
(109) |
Jul
(70) |
Aug
(22) |
Sep
(19) |
Oct
(4) |
Nov
(25) |
Dec
(46) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(68) |
Feb
(52) |
Mar
(54) |
Apr
(57) |
May
(13) |
Jun
(15) |
Jul
(16) |
Aug
(3) |
Sep
(43) |
Oct
(95) |
Nov
(106) |
Dec
(142) |
| 2005 |
Jan
(62) |
Feb
(190) |
Mar
(75) |
Apr
(117) |
May
(123) |
Jun
(64) |
Jul
(122) |
Aug
(95) |
Sep
(63) |
Oct
(102) |
Nov
(99) |
Dec
(85) |
| 2006 |
Jan
(59) |
Feb
(64) |
Mar
(138) |
Apr
(82) |
May
(62) |
Jun
(62) |
Jul
(72) |
Aug
(50) |
Sep
(21) |
Oct
(95) |
Nov
(95) |
Dec
(29) |
| 2007 |
Jan
(26) |
Feb
(36) |
Mar
(45) |
Apr
(12) |
May
(53) |
Jun
(38) |
Jul
(19) |
Aug
(87) |
Sep
(63) |
Oct
(272) |
Nov
(102) |
Dec
(63) |
| 2008 |
Jan
(54) |
Feb
(19) |
Mar
(84) |
Apr
(111) |
May
(17) |
Jun
(26) |
Jul
(18) |
Aug
(10) |
Sep
(14) |
Oct
(9) |
Nov
(4) |
Dec
(12) |
| 2009 |
Jan
(5) |
Feb
(7) |
Mar
(4) |
Apr
(8) |
May
(4) |
Jun
(7) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(6) |
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Masakazu N. <n-...@md...> - 2003-06-19 01:44:24
|
sorry have a bit mistake ;-) when your client IP is 192.168.1.1 like that :-) [iaxclient] type=friend context=default secret=testpassword permit=192.168.1.1/255.255.255.0 or permit=0.0.0.0/0.0.0.0 and register string is iaxclient:testpassword@192.168.1.2 --- Masakazu Nakano. Dairiten.com - an open source VoIP and Ubiquitous Portal site in Japan. http://www.dairiten.com/modules/news/ powered by xoops at http://www.xoops.org On Thu, 19 Jun 2003 01:21:29 +0000 "Shore Linux Solutions" <sho...@ho...> wrote: >I downloaded the iaxclient binary for my RedHat 8.0 box. I then executed >the script, went under the register option and entered my information. I >then went to my iax.conf file and made an entry like so: > [iaxclient] > type=friend > context=default > username=testuser > secret=testpassword > host=192.168.1.1 > >The client box ip is 192.168.1.1, the host ip is 192.168.1.2 The entry >that I put in the registry field is like so: > testuser:testpassword@192.168.1.2 > >When I try to make a call the message that appears on the screen is >"registration rejected". Any assistance would be greatly appreciated. >AJ > >_________________________________________________________________ >MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. >http://join.msn.com/?page=features/virus > > > >------------------------------------------------------- >This SF.Net email is sponsored by: INetU >Attention Web Developers & Consultants: Become An INetU Hosting Partner. >Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! >INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php >_______________________________________________ >Iaxclient-devel mailing list >Iax...@li... >https://lists.sourceforge.net/lists/listinfo/iaxclient-devel |
|
From: Faizan T. <fa...@ti...> - 2003-06-19 01:40:16
|
hi. also why dont you just make your host dynamic. host=dynamic ----- Original Message ----- From: "Shore Linux Solutions" <sho...@ho...> To: <iax...@li...> Sent: Thursday, June 19, 2003 6:21 AM Subject: [Iaxclient-devel] unable to register > I downloaded the iaxclient binary for my RedHat 8.0 box. I then executed > the script, went under the register option and entered my information. I > then went to my iax.conf file and made an entry like so: > [iaxclient] > type=friend > context=default > username=testuser > secret=testpassword > host=192.168.1.1 > > The client box ip is 192.168.1.1, the host ip is 192.168.1.2 The entry > that I put in the registry field is like so: > testuser:testpassword@192.168.1.2 > > When I try to make a call the message that appears on the screen is > "registration rejected". Any assistance would be greatly appreciated. > AJ > > _________________________________________________________________ > MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. > http://join.msn.com/?page=features/virus > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > Iaxclient-devel mailing list > Iax...@li... > https://lists.sourceforge.net/lists/listinfo/iaxclient-devel |
|
From: Faizan T. <fa...@ti...> - 2003-06-19 01:40:13
|
hi. register like this. iaxclient:testpassword@192.168.1.2 ----- Original Message ----- From: "Shore Linux Solutions" <sho...@ho...> To: <iax...@li...> Sent: Thursday, June 19, 2003 6:21 AM Subject: [Iaxclient-devel] unable to register > I downloaded the iaxclient binary for my RedHat 8.0 box. I then executed > the script, went under the register option and entered my information. I > then went to my iax.conf file and made an entry like so: > [iaxclient] > type=friend > context=default > username=testuser > secret=testpassword > host=192.168.1.1 > > The client box ip is 192.168.1.1, the host ip is 192.168.1.2 The entry > that I put in the registry field is like so: > testuser:testpassword@192.168.1.2 > > When I try to make a call the message that appears on the screen is > "registration rejected". Any assistance would be greatly appreciated. > AJ > > _________________________________________________________________ > MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. > http://join.msn.com/?page=features/virus > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > Iaxclient-devel mailing list > Iax...@li... > https://lists.sourceforge.net/lists/listinfo/iaxclient-devel |
|
From: Masakazu N. <n-...@md...> - 2003-06-19 01:31:55
|
when your client IP is 192.168.1.2 like that :-) [iaxclient] type=friend context=default secret=testpassword permit=192.168.1.2/255.255.255.0 or permit=0.0.0.0/0.0.0.0 and register string is iaxclient:testpassword@192.168.1.2 --- Masakazu Nakano. Dairiten.com - an open source VoIP and Ubiquitous Portal site in Japan. http://www.dairiten.com/modules/news/ powered by xoops at http://www.xoops.org On Thu, 19 Jun 2003 01:21:29 +0000 "Shore Linux Solutions" <sho...@ho...> wrote: >I downloaded the iaxclient binary for my RedHat 8.0 box. I then executed >the script, went under the register option and entered my information. I >then went to my iax.conf file and made an entry like so: > [iaxclient] > type=friend > context=default > username=testuser > secret=testpassword > host=192.168.1.1 > >The client box ip is 192.168.1.1, the host ip is 192.168.1.2 The entry >that I put in the registry field is like so: > testuser:testpassword@192.168.1.2 > >When I try to make a call the message that appears on the screen is >"registration rejected". Any assistance would be greatly appreciated. >AJ > >_________________________________________________________________ >MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. >http://join.msn.com/?page=features/virus > > > >------------------------------------------------------- >This SF.Net email is sponsored by: INetU >Attention Web Developers & Consultants: Become An INetU Hosting Partner. >Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! >INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php >_______________________________________________ >Iaxclient-devel mailing list >Iax...@li... >https://lists.sourceforge.net/lists/listinfo/iaxclient-devel |
|
From: Shore L. S. <sho...@ho...> - 2003-06-19 01:21:36
|
I downloaded the iaxclient binary for my RedHat 8.0 box. I then executed
the script, went under the register option and entered my information. I
then went to my iax.conf file and made an entry like so:
[iaxclient]
type=friend
context=default
username=testuser
secret=testpassword
host=192.168.1.1
The client box ip is 192.168.1.1, the host ip is 192.168.1.2 The entry
that I put in the registry field is like so:
testuser:testpassword@192.168.1.2
When I try to make a call the message that appears on the screen is
"registration rejected". Any assistance would be greatly appreciated.
AJ
_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
http://join.msn.com/?page=features/virus
|
|
From: Steve K. <st...@st...> - 2003-06-18 21:47:14
|
The platform-dependent bugs from yesterday's work have been fixed.
Everything seems to be working properly now, across platforms. Multiple
calls, registration, the works.
Just as a note: At any minute now, I might be disappearing for a week
or two, as my second child (a boy), is due any day now.. So, if y'all
don't see me for a bit, that could be why.
-SteveK
--
Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 - (212) 533-1775
HorizonLive.com - collaborate . interact . learn
"The box said 'Requires Windows 95, NT, or better,' so I installed Linux."
|
|
From: Steve K. <st...@st...> - 2003-06-18 00:00:48
|
Ran a little late today doing platform-specific testing, so there's a
couple of bugs in today's commits.
Here's the commit mesage:
===============================
Another big commit:
1) Replace the "RadioBox" control with a ListCntrl control, for the call
list. This has expandable columns, and displays each data type in it's
own column.
2) Some locking for the library: try to prevent us from doing the
processing loop while moving the calls around from the front-end.
3) REGISTRATION, and better incoming call support.
Incoming calls now are not auto-answered, but are answered when you
select them.
You can register with an IAX server (tested for IAX1 only so far).
===============================
The bugs I've seen so far are:
1) On Windows, if you choose the File->Register menu command, I'm
getting a menu event once per second, like, forever. So, you get lots
of Register dialogs. This is a strange one -- either a wxWindows bug,
or, it might be some kind of memory corruption I have somewhere else.
2) On windows, sometimes the app deadlocks when you quit. shouldn't be
too hard to track down.
3) On MacOSX, with the new call list, you can't click on calls to select
this. This makes things quite unusable.
I may work on the OSX bug tonight, or not. If someonw wants to play
with wxWindows UI stuff, the IAXCalls ui member (derived from
wxListCntrl) might be a good candidate for sprucing up and/or
rewriting).
But, the registration seems to be working for now, and there's better
call state stuff, and it all seems to work perfectly under linux :)
--
Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 - (212) 533-1775
HorizonLive.com - collaborate . interact . learn
"The box said 'Requires Windows 95, NT, or better,' so I installed Linux."
|
|
From: Faizan T. <fa...@ti...> - 2003-06-17 02:16:03
|
Hi.
Well Stevek has already answered everything.=20
To make things more compatible I used Visual C 6.0 and the SDK of Visual =
Studio 6.0.=20
----- Original Message -----=20
From: Uriel Carrasquilla=20
To: 'Faizan Tili' ; 'iaxclient devel'=20
Sent: Monday, June 16, 2003 8:23 AM
Subject: RE: [Iaxclient-devel] iaxclient with MSVC
Faizan:
whe you are developing with MSVC, do you still need to have:
1) Cygwin
2) WxWindows
3) MSVC
Also, are you producing dll's?
When we develop with MinGW, I need point 1 and 2 plus MinGW before I =
can compile GUI applications.
How can I get a copy of the source code for MSVC so I can try it at =
work where I do have access to MSVC.
Regards,
Uriel
-----Original Message-----
From: iax...@li... =
[mailto:iax...@li...]On Behalf Of Faizan =
Tili
Sent: Sunday, June 15, 2003 6:19 PM
To: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
Hi.
Well developing on MSVC is better for windows. GNU C compilers =
mostly give less performance on Windows.=20
But Steve you have already taken much work on you. So I can make it =
less for you by working on windows and you can work with wxWindows for =
all 3 OS. We both can keep merging our code. You are from Linux =
background so I think learning the MSVC way will take time for you as =
MSVC is not standard C ( it even has its own data type). I am from =
Windows Background.=20
So why to stress yourself with more work. Just mail me what you want =
in windows and develop in wxWindows.=20
I think making a client with wxWindows for all 3 is a good idea as =
many ppl working on open source might not have VC and would like to work =
with Open Source tools.
Thanks.
----- Original Message -----=20
From: Steve Kann=20
To: ur...@ad...=20
Cc: 'iaxclient devel'=20
Sent: Sunday, June 15, 2003 6:33 PM
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 07:10 PM, Uriel Carrasquilla wrote:
Steve:
I am debating in my mind if I put my energy into MSVC or MinGW. =
I do come from the Linux world and so far I like what I see with Cygwin =
(feels like home). However, I don't want to be at a disadvantage long =
term and I would seriously consider switching over to MSVC. I would be =
making new friends at work with the Windows cloud.
If I was to have a Linux machine, I would not use iaxclient, I =
would go for the full * (unless a Linux PDA). In my mind, iaxclient's =
best place is the Mac and the Windows environments.
Well, I'd say that getting yourself setup with wxwindows and MinGW =
would be good, because it is most similar environment to that used to =
build for Linux and MacOSX. Also, since it's free, it might be more =
accessible to people.
Of course, it would help if we had better step-by-step directions =
to get people set up with this. I'm hoping that as more people get it =
set up, they can help with this. Darren "]data[" got it set up for him, =
although he seems to have taken a slightly different route than I did.
Maybe also we need to make the Makefiles, etc, a little more =
flexible to handle different ways that people might get things set up. =
(Already, I've seen this with MacOSX also).
The "make" for wxWindows has been running for a while now (I did =
not even use the Optimize option). I guess my 320 MHz Celeron is =
getting slow for this type of work.
naah, I have a 300Mhz PII (with just 128Mb ram!) that I'm using. =
More memory would help when linking with wxwindows, though, but it works =
well enough.
I'm sorry that getting setup is so frustrating for now. If people =
do it, and help with "developer docs" for it, it will get easier. Maybe =
we can figure out a way to "script" the setup for people, so they can =
just run some script, and it will get cygwin, MinGW, and wxwindows all =
set up for them on windows, which will make this easier for everyone.
Hang in there!
Regards,
Uriel
-----Original Message-----
From: Steve Kann [mailto:st...@st...]
Sent: Saturday, June 14, 2003 2:36 PM
To: ur...@ad...
Cc: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla =
wrote:
Can we learn more as to what these new changes entail?
What I make out of it is a Microsoft-Visual-C++ version, am I =
correct?
Uriel
Yes, it is one project file to build the library with MSVC, and =
a new Win32 only client, with project files to build under MSVC.
-SteveK
-----Original Message-----
From: iax...@li... =
[mailto:iax...@li...]On Behalf Of Steve =
Kann
Sent: Friday, June 13, 2003 7:46 PM
To: iaxclient devel
Subject: [Iaxclient-devel] iaxclient's first contributor
This is just a note to thank Tili for becoming iaxclient's first =
contributor.
Today, I just committed his contributions, which include some =
portability changes, as well as MSVC project files for the library, and =
a new simple Win32-only client, WinIAX.
These are all available now in CVS. (or should be real soon, =
sourceforge anonymous CVS seems to be lagging a bit -- I think it's =
running on a backup from last night, although the developer CVS access =
is working).
-SteveK
<image.tiff>
|
|
From: Steve K. <st...@st...> - 2003-06-16 23:29:52
|
>From my commit message:
Log Message:
A pretty big commit.
1) Change the overall "event" callback mechanism, to use a
structure/union, with just one callback for all events. clients can
accept or decline each event, in which case the library might take a
"default" action for the event. (currently, the library will ignore all
events except for text, which it will print to stderr/stdout).
2) Totally rework call handling, and allow the library to manage
multiple calls. Call state is more or less followed through the
lifetime of the call, but may not be right in all cases.
3) Implement call appearances based on all of this in wx.
4) Make testcall work with this (only one call).
5) Try to keep Faizan's "WinIAX" client up to date with the API changes,
haven't tested the changes there, but they should work for one
call.
6) #define out the WIN AUDIO stuff, it's pretty far behind now, and
would need some work to get going. portaudio seems to handle
the gory
details for us very nicely.
Need to do more testing with all of this, but this now allows you to
make IAXClient -> IAXClient calls.
Of course, allowing people to reject calls would be nice too, but I
suppose you can always hang up :)
-SteveK
--
Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 - (212) 533-1775
HorizonLive.com - collaborate . interact . learn
"The box said 'Requires Windows 95, NT, or better,' so I installed Linux."
|
|
From: Steve K. <st...@st...> - 2003-06-16 13:40:17
|
I'll answer this now, and Faizan can correct me if i'm wrong:
On Sun, 2003-06-15 at 23:23, Uriel Carrasquilla wrote:
> Faizan:
> whe you are developing with MSVC, do you still need to have:
> 1) Cygwin
No.
> 2) WxWindows
You would to compile the "wx" client, but not if you build only the
WinIAX client. But the WinIAX client is Windows-Only, so any work done
there won't be available on other platforms. (you could duplicate that
work in wx, or we could build other platform-dependent clients).
> 3) MSVC
Yes, of course :)
> Also, are you producing dll's?
Presently, his Project files make a static library, and link that
statically into the application, so "WinIAX.EXE" is a standalone
executable, like "wx.exe"
> When we develop with MinGW, I need point 1 and 2 plus MinGW before I
> can compile GUI applications.
Yes, for "wx". However, if there was a Makefile, you could compile
WinIAX.exe without wxwindows, but it would still be windows-only..
> How can I get a copy of the source code for MSVC so I can try it at
> work where I do have access to MSVC.
To build with MSVC, just check out the sources from CVS, and there's one
"project" file called iaxclient_lib.dsw for the library, and one called
winiax.dsw for the Windows-only client.
You could also make a similar MSVC project for the "wx.cc" client,
and/or testcall.
> Regards,
> Uriel
>
> -----Original Message-----
> From: iax...@li...
> [mailto:iax...@li...]On Behalf
> Of Faizan Tili
> Sent: Sunday, June 15, 2003 6:19 PM
> To: 'iaxclient devel'
> Subject: Re: [Iaxclient-devel] iaxclient's first contributor
>
>
> Hi.
>
> Well developing on MSVC is better for windows. GNU C compilers
> mostly give less performance on Windows.
> But Steve you have already taken much work on you. So I can
> make it less for you by working on windows and you can work
> with wxWindows for all 3 OS. We both can keep merging our
> code. You are from Linux background so I think learning the
> MSVC way will take time for you as MSVC is not standard C ( it
> even has its own data type). I am from Windows Background.
> So why to stress yourself with more work. Just mail me what
> you want in windows and develop in wxWindows.
>
> I think making a client with wxWindows for all 3 is a good
> idea as many ppl working on open source might not have VC and
> would like to work with Open Source tools.
>
> Thanks.
>
> ----- Original Message -----
> From: Steve Kann
> To: ur...@ad...
> Cc: 'iaxclient devel'
> Sent: Sunday, June 15, 2003 6:33 PM
> Subject: Re: [Iaxclient-devel] iaxclient's first
> contributor
>
> On Saturday, June 14, 2003, at 07:10 PM, Uriel
> Carrasquilla wrote:
>
>
> Steve:
> I am debating in my mind if I put my energy
> into MSVC or MinGW. I do come from the Linux
> world and so far I like what I see with Cygwin
> (feels like home). However, I don't want to
> be at a disadvantage long term and I would
> seriously consider switching over to MSVC. I
> would be making new friends at work with the
> Windows cloud.
> If I was to have a Linux machine, I would not
> use iaxclient, I would go for the full *
> (unless a Linux PDA). In my mind, iaxclient's
> best place is the Mac and the Windows
> environments.
>
>
> Well, I'd say that getting yourself setup with
> wxwindows and MinGW would be good, because it is most
> similar environment to that used to build for Linux
> and MacOSX. Also, since it's free, it might be more
> accessible to people.
>
> Of course, it would help if we had better step-by-step
> directions to get people set up with this. I'm hoping
> that as more people get it set up, they can help with
> this. Darren "]data[" got it set up for him, although
> he seems to have taken a slightly different route than
> I did.
>
> Maybe also we need to make the Makefiles, etc, a
> little more flexible to handle different ways that
> people might get things set up. (Already, I've seen
> this with MacOSX also).
>
>
> The "make" for wxWindows has been running for
> a while now (I did not even use the Optimize
> option). I guess my 320 MHz Celeron is
> getting slow for this type of work.
>
>
> naah, I have a 300Mhz PII (with just 128Mb ram!) that
> I'm using. More memory would help when linking with
> wxwindows, though, but it works well enough.
>
>
> I'm sorry that getting setup is so frustrating for
> now. If people do it, and help with "developer docs"
> for it, it will get easier. Maybe we can figure out a
> way to "script" the setup for people, so they can just
> run some script, and it will get cygwin, MinGW, and
> wxwindows all set up for them on windows, which will
> make this easier for everyone.
>
> Hang in there!
>
>
>
>
> Regards,
> Uriel
>
> -----Original Message-----
> From: Steve Kann [mailto:st...@st...]
> Sent: Saturday, June 14, 2003 2:36 PM
> To: ur...@ad...
> Cc: 'iaxclient devel'
> Subject: Re: [Iaxclient-devel] iaxclient's
> first contributor
>
>
> On Saturday, June 14, 2003, at 02:56 AM, Uriel
> Carrasquilla wrote:
>
> Can we learn more as to what these new changes
> entail?
> What I make out of it is a
> Microsoft-Visual-C++ version, am I correct?
> Uriel
>
>
> Yes, it is one project file to build the
> library with MSVC, and a new Win32 only
> client, with project files to build under
> MSVC.
>
> -SteveK
>
>
>
> -----Original Message-----
> From:
> iax...@li...
> [mailto:iax...@li...]On Behalf Of Steve Kann
> Sent: Friday, June 13, 2003 7:46 PM
> To: iaxclient devel
> Subject: [Iaxclient-devel] iaxclient's first
> contributor
>
>
> This is just a note to thank Tili for becoming
> iaxclient's first contributor.
>
> Today, I just committed his contributions,
> which include some portability changes, as
> well as MSVC project files for the library,
> and a new simple Win32-only client, WinIAX.
>
> These are all available now in CVS. (or
> should be real soon, sourceforge anonymous CVS
> seems to be lagging a bit -- I think it's
> running on a backup from last night, although
> the developer CVS access is working).
>
> -SteveK
>
>
> <image.tiff>
>
--
Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 - (212) 533-1775
HorizonLive.com - collaborate . interact . learn
"The box said 'Requires Windows 95, NT, or better,' so I installed Linux."
|
|
From: Steve K. <st...@st...> - 2003-06-16 13:33:31
|
Yup, you applied that one, and the buf[len - 1] thing, but didn't apply the other changes I sent you. Attached is a patch which: 1) synchronizes iax2.h with necessary definitions from asterisk (COMMAND_TRANSFER, IE_RDNIS), which are used in the parser. 2) portability fixes for compilation on MacOSX and Win32 (mostly header re-ordering and conditionalization, plus a macro for IAX_SOCKOPTS). 3) Also includes my proposed change for stack ordering on MacOSX (you can replace this part with your proposed solution instead). -SteveK On Sat, 2003-06-14 at 10:57, Mark Spencer wrote: > Should be applied, please make sure i didn't break anything :) > > Mark > > On 12 Jun 2003, Steve Kann wrote: > > > Index: iax.c > > =================================================================== > > RCS file: /cvsroot/iaxclient/iaxclient/lib/libiax2/src/iax.c,v > > retrieving revision 1.5 > > diff -u -r1.5 iax.c > > --- iax.c 12 Jun 2003 14:54:33 -0000 1.5 > > +++ iax.c 12 Jun 2003 19:01:24 -0000 > > @@ -1583,6 +1583,8 @@ > > } > > if (username) > > iax_ie_append_str(&ied, IAX_IE_USERNAME, username); > > + if (exten && strlen(exten)) > > + iax_ie_append_str(&ied, IAX_IE_CALLED_NUMBER, exten); > > if (dnid && strlen(dnid)) > > iax_ie_append_str(&ied, IAX_IE_DNID, dnid); > > if (context && strlen(context)) > > > > -- > > Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 - (212) 533-1775 > > HorizonLive.com - collaborate . interact . learn > > "The box said 'Requires Windows 95, NT, or better,' so I installed Linux." > > -- Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 - (212) 533-1775 HorizonLive.com - collaborate . interact . learn "The box said 'Requires Windows 95, NT, or better,' so I installed Linux." |
|
From: Steve K. <st...@st...> - 2003-06-16 13:25:36
|
On Sun, 2003-06-15 at 20:00, Uriel Carrasquilla wrote:
> Steve:
> 1) I move the wxWindows directory and renamed it to c:\wx - it seems
> to me that existing c:\Cygwin\usr\src\wxWindow location might be a
> problem. The name wxWindows for the directory seems to be a problem
> as well.
> 2) I changed the WXWIN environment variable to point to this new
> location i.e. c:\wx
either of these paths seems OK, but the WXWIN environment variable needs
to have forward slashes and not backslashes. I.e. "C:/wx" instead of
"C:\wx".
I think that's your whole problem with the includes, below.
-SteveK
>
> When I issue make>&make.txt (from
> c:\Cygwin\usr\src\iaxclient\simpleclient\wx\) I get the following
> messages.
> it is telling me that it cannot find:
> wx/wxprec.h
> wx/wx.h
> plus pages and pages of errors. Like you are saying, the wxWindow
> file headers "h" are not being found.
>
> The files are being "included" from wx.cc which resides in the same
> directory as the Makefile I am using when I issue "make".
>
> When I search "c:\wc" I can see these two files exist in
> c:\wx\include\wx\
>
> When I look at the content of my
> c:\Cygwin\usr\src\iaxclient\simpleclient\wx I see the following
> files:
> 1) Makefile (which happens to be the one I am executing. Inside it I
> see no reference whatsoever to wx/include or WXWIN environment
> variable with the /include).
> 2) wx.cc (which is being included by the Makefile. This file contains
> an "include" for the wx/wxprec.h and wx/wx.h)
> 3) wx.h (isn't this file conflicting with the wx/wx.h in the
> c:\wx\include\wx.h)
>
> I either have my files organized in a way that the "make" using
> Makefile does not understand, or the Makefile is not complete, or the
> wx.cc should be using the WXWIN environment variable for the "include"
> statement to include wx/include/wxprec.h instead of wx/wxprec.h.
>
> Before I start making my own decisions and change the Makefile and
> wx.cc file, I would like to consult with you what is the best
> approach:
> 1) rename all of directories and arrange files in a format that the
> Makefile is expecting? what would this format be so I don't have to
> do it by trial and error.
> 2) introduce the WXWIN variable in the "include" statements of the
> source in iaxclient/simpleclient/wx source "c" and header "h" files?
> 3) make the Makefile more intelligent?
>
> Hoping to hear from you soon,
> URiel
>
> -----Original Message-----
> From: iax...@li...
> [mailto:iax...@li...]On Behalf Of Steve
> Kann
> Sent: Sunday, June 15, 2003 9:39 AM
> To: ur...@ad...
> Cc: 'iaxclient devel'
> Subject: Re: [Iaxclient-devel] iaxclient wxWindows MinGW compile
>
>
>
> On Sunday, June 15, 2003, at 02:02 AM, Uriel Carrasquilla
> wrote:
>
>
> Steve:
> I am still having problems with the
> /iaxclient/simpleclient/wx compile.
> I installed wxWindows:
> 1) set up the WXWIN envronment variable to point to
> the root of where wxWindows is located.
> (c:\Cygwin\usr\src\wxWindows)
> 2) edited src/make95.env to basically have MINGW32=1
> and MINGW32VERSION=1 (after verifying with gcc
> --version).
> 3) executed "make -f makefile.g95" from /src/msw and
> from /samples/minimal.
>
> It all seems to all have run OK. I did check that I
> could use the Unix commands "cp", "mv" and "rm".
> is there a way to verify that the wxWindows installed
> properly?
>
> I also checked in the iaxclient/simpleclient/wx
> Makefile that the WXWIN variable is pointing to a
> correct subdirectory that exists.
>
> Then I went to
> c:Cygwin/usr/src/iaxcient/simpleclient/wx, did a "make
> clean" followed by "make".
> After a lot of scrolling I get the message *** error 1
> in wx.o.
> It is 1:15 AM so I am going to call it a quit.
>
>
> As usual with development (and compiling/linking errors), it's
> usually the "first" errors that are important, not the last.
>
> If you're using cygwin, you should be able to scroll back and
> see the first error messages. Otherwise, you can so something
> like make >& make.OUT, then look at the file make.OUT to see
> what happened.
>
> Most likely, it still isn't finding some header file, because
> perhaps you don't have a complete wxwindows install. (or, you
> somehow have a "different" wxwindows install than I do, and my
> Makefiles aren't flexible enough to handle it.
>
> One thing I remembered from working with data, is that you are
> probably better off specifying the WXWIN directory as
> "C:/wxwindows-2.4" or something, instead of using the "cygwin"
> path, like /cygdrive/c/wxwindows-2.4". This is because the
> MinGW compiler doesn't necessarily understand the same "mount
> points" as the cygwin shell does, unless you've set them up to
> be the same. This was one thing that "got" Darren when he was
> doing this, but I didn't see because I initially set WXWIN via
> "C:/". (just use the "windows" path, but use forward slashes
> instead of backslashes).
>
> That might be your current problem?
>
> -SteveK
>
>
>
> Suggestions will be great!
> Regards,
> Uriel
>
> -----Original Message-----
> From: iax...@li...
> [mailto:iax...@li...]On
> Behalf Of Uriel Carrasquilla
> Sent: Saturday, June 14, 2003 7:10 PM
> To: 'Steve Kann'
> Cc: 'iaxclient devel'
> Subject: RE: [Iaxclient-devel] iaxclient's first
> contributor
>
> Steve:
> I am debating in my mind if I put my energy into MSVC
> or MinGW. I do come from the Linux world and so far I
> like what I see with Cygwin (feels like home).
> However, I don't want to be at a disadvantage long
> term and I would seriously consider switching over to
> MSVC. I would be making new friends at work with the
> Windows cloud.
> If I was to have a Linux machine, I would not use
> iaxclient, I would go for the full * (unless a Linux
> PDA). In my mind, iaxclient's best place is the Mac
> and the Windows environments.
>
> The "make" for wxWindows has been running for a while
> now (I did not even use the Optimize option). I guess
> my 320 MHz Celeron is getting slow for this type of
> work.
>
> Regards,
> Uriel
>
> -----Original Message-----
> From: Steve Kann [mailto:st...@st...]
> Sent: Saturday, June 14, 2003 2:36 PM
> To: ur...@ad...
> Cc: 'iaxclient devel'
> Subject: Re: [Iaxclient-devel] iaxclient's first
> contributor
>
>
> On Saturday, June 14, 2003, at 02:56 AM, Uriel
> Carrasquilla wrote:
>
> Can we learn more as to what these new changes entail?
> What I make out of it is a Microsoft-Visual-C++
> version, am I correct?
> Uriel
>
>
> Yes, it is one project file to build the library with
> MSVC, and a new Win32 only client, with project files
> to build under MSVC.
>
> -SteveK
>
>
>
> -----Original Message-----
> From: iax...@li...
> [mailto:iax...@li...]On
> Behalf Of Steve Kann
> Sent: Friday, June 13, 2003 7:46 PM
> To: iaxclient devel
> Subject: [Iaxclient-devel] iaxclient's first
> contributor
>
>
> This is just a note to thank Tili for becoming
> iaxclient's first contributor.
>
> Today, I just committed his contributions, which
> include some portability changes, as well as MSVC
> project files for the library, and a new simple
> Win32-only client, WinIAX.
>
> These are all available now in CVS. (or should be
> real soon, sourceforge anonymous CVS seems to be
> lagging a bit -- I think it's running on a backup from
> last night, although the developer CVS access is
> working).
>
> -SteveK
>
>
> <image.tiff>
>
--
Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 - (212) 533-1775
HorizonLive.com - collaborate . interact . learn
"The box said 'Requires Windows 95, NT, or better,' so I installed Linux."
|
|
From: Uriel C. <ur...@ad...> - 2003-06-16 02:44:57
|
Faizan:
whe you are developing with MSVC, do you still need to have:
1) Cygwin
2) WxWindows
3) MSVC
Also, are you producing dll's?
When we develop with MinGW, I need point 1 and 2 plus MinGW before I can
compile GUI applications.
How can I get a copy of the source code for MSVC so I can try it at work
where I do have access to MSVC.
Regards,
Uriel
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Faizan Tili
Sent: Sunday, June 15, 2003 6:19 PM
To: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
Hi.
Well developing on MSVC is better for windows. GNU C compilers mostly give
less performance on Windows.
But Steve you have already taken much work on you. So I can make it less
for you by working on windows and you can work with wxWindows for all 3 OS.
We both can keep merging our code. You are from Linux background so I think
learning the MSVC way will take time for you as MSVC is not standard C ( it
even has its own data type). I am from Windows Background.
So why to stress yourself with more work. Just mail me what you want in
windows and develop in wxWindows.
I think making a client with wxWindows for all 3 is a good idea as many
ppl working on open source might not have VC and would like to work with
Open Source tools.
Thanks.
----- Original Message -----
From: Steve Kann
To: ur...@ad...
Cc: 'iaxclient devel'
Sent: Sunday, June 15, 2003 6:33 PM
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 07:10 PM, Uriel Carrasquilla wrote:
Steve:
I am debating in my mind if I put my energy into MSVC or MinGW. I do
come from the Linux world and so far I like what I see with Cygwin (feels
like home). However, I don't want to be at a disadvantage long term and I
would seriously consider switching over to MSVC. I would be making new
friends at work with the Windows cloud.
If I was to have a Linux machine, I would not use iaxclient, I would
go for the full * (unless a Linux PDA). In my mind, iaxclient's best place
is the Mac and the Windows environments.
Well, I'd say that getting yourself setup with wxwindows and MinGW would
be good, because it is most similar environment to that used to build for
Linux and MacOSX. Also, since it's free, it might be more accessible to
people.
Of course, it would help if we had better step-by-step directions to get
people set up with this. I'm hoping that as more people get it set up, they
can help with this. Darren "]data[" got it set up for him, although he seems
to have taken a slightly different route than I did.
Maybe also we need to make the Makefiles, etc, a little more flexible to
handle different ways that people might get things set up. (Already, I've
seen this with MacOSX also).
The "make" for wxWindows has been running for a while now (I did not
even use the Optimize option). I guess my 320 MHz Celeron is getting slow
for this type of work.
naah, I have a 300Mhz PII (with just 128Mb ram!) that I'm using. More
memory would help when linking with wxwindows, though, but it works well
enough.
I'm sorry that getting setup is so frustrating for now. If people do it,
and help with "developer docs" for it, it will get easier. Maybe we can
figure out a way to "script" the setup for people, so they can just run some
script, and it will get cygwin, MinGW, and wxwindows all set up for them on
windows, which will make this easier for everyone.
Hang in there!
Regards,
Uriel
-----Original Message-----
From: Steve Kann [mailto:st...@st...]
Sent: Saturday, June 14, 2003 2:36 PM
To: ur...@ad...
Cc: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla wrote:
Can we learn more as to what these new changes entail?
What I make out of it is a Microsoft-Visual-C++ version, am I correct?
Uriel
Yes, it is one project file to build the library with MSVC, and a new
Win32 only client, with project files to build under MSVC.
-SteveK
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Steve Kann
Sent: Friday, June 13, 2003 7:46 PM
To: iaxclient devel
Subject: [Iaxclient-devel] iaxclient's first contributor
This is just a note to thank Tili for becoming iaxclient's first
contributor.
Today, I just committed his contributions, which include some
portability changes, as well as MSVC project files for the library, and a
new simple Win32-only client, WinIAX.
These are all available now in CVS. (or should be real soon,
sourceforge anonymous CVS seems to be lagging a bit -- I think it's running
on a backup from last night, although the developer CVS access is working).
-SteveK
<image.tiff>
|
|
From: Uriel C. <ur...@ad...> - 2003-06-15 23:21:28
|
Steve:
1) I move the wxWindows directory and renamed it to c:\wx - it seems to me
that existing c:\Cygwin\usr\src\wxWindow location might be a problem. The
name wxWindows for the directory seems to be a problem as well.
2) I changed the WXWIN environment variable to point to this new location
i.e. c:\wx
When I issue make>&make.txt (from
c:\Cygwin\usr\src\iaxclient\simpleclient\wx\) I get the following messages.
it is telling me that it cannot find:
wx/wxprec.h
wx/wx.h
plus pages and pages of errors. Like you are saying, the wxWindow file
headers "h" are not being found.
The files are being "included" from wx.cc which resides in the same
directory as the Makefile I am using when I issue "make".
When I search "c:\wc" I can see these two files exist in c:\wx\include\wx\
When I look at the content of my c:\Cygwin\usr\src\iaxclient\simpleclient\wx
I see the following files:
1) Makefile (which happens to be the one I am executing. Inside it I see
no reference whatsoever to wx/include or WXWIN environment variable with the
/include).
2) wx.cc (which is being included by the Makefile. This file contains an
"include" for the wx/wxprec.h and wx/wx.h)
3) wx.h (isn't this file conflicting with the wx/wx.h in the
c:\wx\include\wx.h)
I either have my files organized in a way that the "make" using Makefile
does not understand, or the Makefile is not complete, or the wx.cc should be
using the WXWIN environment variable for the "include" statement to include
wx/include/wxprec.h instead of wx/wxprec.h.
Before I start making my own decisions and change the Makefile and wx.cc
file, I would like to consult with you what is the best approach:
1) rename all of directories and arrange files in a format that the Makefile
is expecting? what would this format be so I don't have to do it by trial
and error.
2) introduce the WXWIN variable in the "include" statements of the source in
iaxclient/simpleclient/wx source "c" and header "h" files?
3) make the Makefile more intelligent?
Hoping to hear from you soon,
URiel
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Steve Kann
Sent: Sunday, June 15, 2003 9:39 AM
To: ur...@ad...
Cc: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient wxWindows MinGW compile
On Sunday, June 15, 2003, at 02:02 AM, Uriel Carrasquilla wrote:
Steve:
I am still having problems with the /iaxclient/simpleclient/wx compile.
I installed wxWindows:
1) set up the WXWIN envronment variable to point to the root of where
wxWindows is located. (c:\Cygwin\usr\src\wxWindows)
2) edited src/make95.env to basically have MINGW32=1 and
MINGW32VERSION=1 (after verifying with gcc --version).
3) executed "make -f makefile.g95" from /src/msw and from
/samples/minimal.
It all seems to all have run OK. I did check that I could use the Unix
commands "cp", "mv" and "rm".
is there a way to verify that the wxWindows installed properly?
I also checked in the iaxclient/simpleclient/wx Makefile that the WXWIN
variable is pointing to a correct subdirectory that exists.
Then I went to c:Cygwin/usr/src/iaxcient/simpleclient/wx, did a "make
clean" followed by "make".
After a lot of scrolling I get the message *** error 1 in wx.o.
It is 1:15 AM so I am going to call it a quit.
As usual with development (and compiling/linking errors), it's usually the
"first" errors that are important, not the last.
If you're using cygwin, you should be able to scroll back and see the
first error messages. Otherwise, you can so something like make >& make.OUT,
then look at the file make.OUT to see what happened.
Most likely, it still isn't finding some header file, because perhaps you
don't have a complete wxwindows install. (or, you somehow have a "different"
wxwindows install than I do, and my Makefiles aren't flexible enough to
handle it.
One thing I remembered from working with data, is that you are probably
better off specifying the WXWIN directory as "C:/wxwindows-2.4" or
something, instead of using the "cygwin" path, like
/cygdrive/c/wxwindows-2.4". This is because the MinGW compiler doesn't
necessarily understand the same "mount points" as the cygwin shell does,
unless you've set them up to be the same. This was one thing that "got"
Darren when he was doing this, but I didn't see because I initially set
WXWIN via "C:/". (just use the "windows" path, but use forward slashes
instead of backslashes).
That might be your current problem?
-SteveK
Suggestions will be great!
Regards,
Uriel
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Uriel
Carrasquilla
Sent: Saturday, June 14, 2003 7:10 PM
To: 'Steve Kann'
Cc: 'iaxclient devel'
Subject: RE: [Iaxclient-devel] iaxclient's first contributor
Steve:
I am debating in my mind if I put my energy into MSVC or MinGW. I do
come from the Linux world and so far I like what I see with Cygwin (feels
like home). However, I don't want to be at a disadvantage long term and I
would seriously consider switching over to MSVC. I would be making new
friends at work with the Windows cloud.
If I was to have a Linux machine, I would not use iaxclient, I would go
for the full * (unless a Linux PDA). In my mind, iaxclient's best place is
the Mac and the Windows environments.
The "make" for wxWindows has been running for a while now (I did not
even use the Optimize option). I guess my 320 MHz Celeron is getting slow
for this type of work.
Regards,
Uriel
-----Original Message-----
From: Steve Kann [mailto:st...@st...]
Sent: Saturday, June 14, 2003 2:36 PM
To: ur...@ad...
Cc: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla wrote:
Can we learn more as to what these new changes entail?
What I make out of it is a Microsoft-Visual-C++ version, am I correct?
Uriel
Yes, it is one project file to build the library with MSVC, and a new
Win32 only client, with project files to build under MSVC.
-SteveK
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Steve Kann
Sent: Friday, June 13, 2003 7:46 PM
To: iaxclient devel
Subject: [Iaxclient-devel] iaxclient's first contributor
This is just a note to thank Tili for becoming iaxclient's first
contributor.
Today, I just committed his contributions, which include some
portability changes, as well as MSVC project files for the library, and a
new simple Win32-only client, WinIAX.
These are all available now in CVS. (or should be real soon,
sourceforge anonymous CVS seems to be lagging a bit -- I think it's running
on a backup from last night, although the developer CVS access is working).
-SteveK
<image.tiff>
|
|
From: Faizan T. <fa...@ti...> - 2003-06-15 22:18:51
|
Hi.
Well developing on MSVC is better for windows. GNU C compilers mostly =
give less performance on Windows.=20
But Steve you have already taken much work on you. So I can make it less =
for you by working on windows and you can work with wxWindows for all 3 =
OS. We both can keep merging our code. You are from Linux background so =
I think learning the MSVC way will take time for you as MSVC is not =
standard C ( it even has its own data type). I am from Windows =
Background.=20
So why to stress yourself with more work. Just mail me what you want in =
windows and develop in wxWindows.=20
I think making a client with wxWindows for all 3 is a good idea as many =
ppl working on open source might not have VC and would like to work with =
Open Source tools.
Thanks.
----- Original Message -----=20
From: Steve Kann=20
To: ur...@ad...=20
Cc: 'iaxclient devel'=20
Sent: Sunday, June 15, 2003 6:33 PM
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 07:10 PM, Uriel Carrasquilla wrote:
Steve:
I am debating in my mind if I put my energy into MSVC or MinGW. I =
do come from the Linux world and so far I like what I see with Cygwin =
(feels like home). However, I don't want to be at a disadvantage long =
term and I would seriously consider switching over to MSVC. I would be =
making new friends at work with the Windows cloud.
If I was to have a Linux machine, I would not use iaxclient, I would =
go for the full * (unless a Linux PDA). In my mind, iaxclient's best =
place is the Mac and the Windows environments.
Well, I'd say that getting yourself setup with wxwindows and MinGW =
would be good, because it is most similar environment to that used to =
build for Linux and MacOSX. Also, since it's free, it might be more =
accessible to people.
Of course, it would help if we had better step-by-step directions to =
get people set up with this. I'm hoping that as more people get it set =
up, they can help with this. Darren "]data[" got it set up for him, =
although he seems to have taken a slightly different route than I did.
Maybe also we need to make the Makefiles, etc, a little more flexible =
to handle different ways that people might get things set up. (Already, =
I've seen this with MacOSX also).
The "make" for wxWindows has been running for a while now (I did not =
even use the Optimize option). I guess my 320 MHz Celeron is getting =
slow for this type of work.
naah, I have a 300Mhz PII (with just 128Mb ram!) that I'm using. More =
memory would help when linking with wxwindows, though, but it works well =
enough.
I'm sorry that getting setup is so frustrating for now. If people do =
it, and help with "developer docs" for it, it will get easier. Maybe we =
can figure out a way to "script" the setup for people, so they can just =
run some script, and it will get cygwin, MinGW, and wxwindows all set up =
for them on windows, which will make this easier for everyone.
Hang in there!
Regards,
Uriel
-----Original Message-----
From: Steve Kann [mailto:st...@st...]
Sent: Saturday, June 14, 2003 2:36 PM
To: ur...@ad...
Cc: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla wrote:
Can we learn more as to what these new changes entail?
What I make out of it is a Microsoft-Visual-C++ version, am I =
correct?
Uriel
Yes, it is one project file to build the library with MSVC, and a =
new Win32 only client, with project files to build under MSVC.
-SteveK
-----Original Message-----
From: iax...@li... =
[mailto:iax...@li...]On Behalf Of Steve =
Kann
Sent: Friday, June 13, 2003 7:46 PM
To: iaxclient devel
Subject: [Iaxclient-devel] iaxclient's first contributor
This is just a note to thank Tili for becoming iaxclient's first =
contributor.
Today, I just committed his contributions, which include some =
portability changes, as well as MSVC project files for the library, and =
a new simple Win32-only client, WinIAX.
These are all available now in CVS. (or should be real soon, =
sourceforge anonymous CVS seems to be lagging a bit -- I think it's =
running on a backup from last night, although the developer CVS access =
is working).
-SteveK
<image.tiff>
|
|
From: Uriel C. <ur...@ad...> - 2003-06-15 15:31:52
|
Let me try this out.
I volunteered with the documentation and I am keeping notes on everything so
we can trace back including some suggested changes in the Makefile.
Regards,
Uriel
-----Original Message-----
From: Steve Kann [mailto:st...@st...]
Sent: Sunday, June 15, 2003 9:39 AM
To: ur...@ad...
Cc: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient wxWindows MinGW compile
On Sunday, June 15, 2003, at 02:02 AM, Uriel Carrasquilla wrote:
Steve:
I am still having problems with the /iaxclient/simpleclient/wx compile.
I installed wxWindows:
1) set up the WXWIN envronment variable to point to the root of where
wxWindows is located. (c:\Cygwin\usr\src\wxWindows)
2) edited src/make95.env to basically have MINGW32=1 and
MINGW32VERSION=1 (after verifying with gcc --version).
3) executed "make -f makefile.g95" from /src/msw and from
/samples/minimal.
It all seems to all have run OK. I did check that I could use the Unix
commands "cp", "mv" and "rm".
is there a way to verify that the wxWindows installed properly?
I also checked in the iaxclient/simpleclient/wx Makefile that the WXWIN
variable is pointing to a correct subdirectory that exists.
Then I went to c:Cygwin/usr/src/iaxcient/simpleclient/wx, did a "make
clean" followed by "make".
After a lot of scrolling I get the message *** error 1 in wx.o.
It is 1:15 AM so I am going to call it a quit.
As usual with development (and compiling/linking errors), it's usually the
"first" errors that are important, not the last.
If you're using cygwin, you should be able to scroll back and see the
first error messages. Otherwise, you can so something like make >& make.OUT,
then look at the file make.OUT to see what happened.
Most likely, it still isn't finding some header file, because perhaps you
don't have a complete wxwindows install. (or, you somehow have a "different"
wxwindows install than I do, and my Makefiles aren't flexible enough to
handle it.
One thing I remembered from working with data, is that you are probably
better off specifying the WXWIN directory as "C:/wxwindows-2.4" or
something, instead of using the "cygwin" path, like
/cygdrive/c/wxwindows-2.4". This is because the MinGW compiler doesn't
necessarily understand the same "mount points" as the cygwin shell does,
unless you've set them up to be the same. This was one thing that "got"
Darren when he was doing this, but I didn't see because I initially set
WXWIN via "C:/". (just use the "windows" path, but use forward slashes
instead of backslashes).
That might be your current problem?
-SteveK
Suggestions will be great!
Regards,
Uriel
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Uriel
Carrasquilla
Sent: Saturday, June 14, 2003 7:10 PM
To: 'Steve Kann'
Cc: 'iaxclient devel'
Subject: RE: [Iaxclient-devel] iaxclient's first contributor
Steve:
I am debating in my mind if I put my energy into MSVC or MinGW. I do
come from the Linux world and so far I like what I see with Cygwin (feels
like home). However, I don't want to be at a disadvantage long term and I
would seriously consider switching over to MSVC. I would be making new
friends at work with the Windows cloud.
If I was to have a Linux machine, I would not use iaxclient, I would go
for the full * (unless a Linux PDA). In my mind, iaxclient's best place is
the Mac and the Windows environments.
The "make" for wxWindows has been running for a while now (I did not
even use the Optimize option). I guess my 320 MHz Celeron is getting slow
for this type of work.
Regards,
Uriel
-----Original Message-----
From: Steve Kann [mailto:st...@st...]
Sent: Saturday, June 14, 2003 2:36 PM
To: ur...@ad...
Cc: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla wrote:
Can we learn more as to what these new changes entail?
What I make out of it is a Microsoft-Visual-C++ version, am I correct?
Uriel
Yes, it is one project file to build the library with MSVC, and a new
Win32 only client, with project files to build under MSVC.
-SteveK
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Steve Kann
Sent: Friday, June 13, 2003 7:46 PM
To: iaxclient devel
Subject: [Iaxclient-devel] iaxclient's first contributor
This is just a note to thank Tili for becoming iaxclient's first
contributor.
Today, I just committed his contributions, which include some
portability changes, as well as MSVC project files for the library, and a
new simple Win32-only client, WinIAX.
These are all available now in CVS. (or should be real soon,
sourceforge anonymous CVS seems to be lagging a bit -- I think it's running
on a backup from last night, although the developer CVS access is working).
-SteveK
<image.tiff>
|
|
From: Steve K. <st...@st...> - 2003-06-15 13:37:56
|
On Sunday, June 15, 2003, at 02:02 AM, Uriel Carrasquilla wrote: > Steve: > I am still having problems with the /iaxclient/simpleclient/wx = compile. > I installed wxWindows: > 1) set up the WXWIN envronment variable to point to the root of where=20= > wxWindows is located. (c:\Cygwin\usr\src\wxWindows) > 2) edited src/make95.env to basically have MINGW32=3D1 and=20 > MINGW32VERSION=3D1 (after verifying with gcc --version). > 3) executed "make -f makefile.g95" from /src/msw and from=20 > /samples/minimal. > =A0 > It all seems to all have run OK.=A0 I did check that I could use the=20= > Unix commands "cp", "mv" and "rm". > is there a way to verify that the wxWindows installed properly? > =A0 > I also checked in the iaxclient/simpleclient/wx Makefile that the=20 > WXWIN variable is pointing to a correct subdirectory that exists. > =A0 > Then I went to c:Cygwin/usr/src/iaxcient/simpleclient/wx, did a "make=20= > clean" followed by "make". > After a lot of scrolling I get the message *** error 1 in wx.o. > It is 1:15 AM so I am going to call it a quit. As usual with development (and compiling/linking errors), it's usually=20= the "first" errors that are important, not the last. If you're using cygwin, you should be able to scroll back and see the=20 first error messages. Otherwise, you can so something like make >&=20 make.OUT, then look at the file make.OUT to see what happened. Most likely, it still isn't finding some header file, because perhaps=20 you don't have a complete wxwindows install. (or, you somehow have a=20 "different" wxwindows install than I do, and my Makefiles aren't=20 flexible enough to handle it. One thing I remembered from working with data, is that you are probably=20= better off specifying the WXWIN directory as "C:/wxwindows-2.4" or=20 something, instead of using the "cygwin" path, like=20 /cygdrive/c/wxwindows-2.4". This is because the MinGW compiler doesn't=20= necessarily understand the same "mount points" as the cygwin shell=20 does, unless you've set them up to be the same. This was one thing=20 that "got" Darren when he was doing this, but I didn't see because I=20 initially set WXWIN via "C:/". (just use the "windows" path, but use=20 forward slashes instead of backslashes). That might be your current problem? -SteveK > Suggestions will be great! > Regards, > Uriel > > -----Original Message----- > From: iax...@li...=20 > [mailto:iax...@li...]On Behalf Of Uriel=20= > Carrasquilla > Sent: Saturday, June 14, 2003 7:10 PM > To: 'Steve Kann' > Cc: 'iaxclient devel' > Subject: RE: [Iaxclient-devel] iaxclient's first contributor > > Steve: > I am debating in my mind if I put my energy into MSVC or MinGW.=A0 I = do=20 > come from the Linux world and so far I like what I see with Cygwin=20 > (feels like home).=A0 However, I don't want to be at a disadvantage = long=20 > term and I would seriously consider switching over to MSVC.=A0 I would=20= > be making new friends at work with the Windows cloud. > If I was to have a Linux machine, I would not use iaxclient, I would=20= > go for the full * (unless a Linux PDA).=A0 In my mind, iaxclient's = best=20 > place is the Mac and the Windows environments. > =A0 > The "make" for wxWindows has been running for a while now (I did not=20= > even use the Optimize option).=A0 I guess my 320 MHz Celeron is = getting=20 > slow for this type of work. > =A0 > Regards, > Uriel > > -----Original Message----- > From: Steve Kann [mailto:st...@st...] > Sent: Saturday, June 14, 2003 2:36 PM > To: ur...@ad... > Cc: 'iaxclient devel' > Subject: Re: [Iaxclient-devel] iaxclient's first contributor > > > On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla wrote: > > Can we learn more as to what these new changes entail? > What I make out of it is a Microsoft-Visual-C++ version, am I correct? > Uriel > > > Yes, it is one project file to build the library with MSVC, and a new=20= > Win32 only client, with project files to build under MSVC. > > -SteveK > > > > -----Original Message----- > From: iax...@li...=20 > [mailto:iax...@li...]On Behalf Of Steve=20= > Kann > Sent: Friday, June 13, 2003 7:46 PM > To: iaxclient devel > Subject: [Iaxclient-devel] iaxclient's first contributor > > > This is just a note to thank Tili for becoming iaxclient's first=20 > contributor. > > Today, I just committed his contributions, which include some=20 > portability changes, as well as MSVC project files for the library,=20 > and a new simple Win32-only client, WinIAX. > > These are all available now in CVS.=A0 (or should be real soon,=20 > sourceforge anonymous CVS seems to be lagging a bit -- I think it's=20 > running on a backup from last night, although the developer CVS access=20= > is working). > > -SteveK > > > <image.tiff> > > > |
|
From: Steve K. <st...@st...> - 2003-06-15 13:32:13
|
On Saturday, June 14, 2003, at 07:10 PM, Uriel Carrasquilla wrote: > Steve: > I am debating in my mind if I put my energy into MSVC or MinGW.=A0 I = do=20 > come from the Linux world and so far I like what I see with Cygwin=20 > (feels like home).=A0 However, I don't want to be at a disadvantage = long=20 > term and I would seriously consider switching over to MSVC.=A0 I would=20= > be making new friends at work with the Windows cloud. > If I was to have a Linux machine, I would not use iaxclient, I would=20= > go for the full * (unless a Linux PDA).=A0 In my mind, iaxclient's = best=20 > place is the Mac and the Windows environments. Well, I'd say that getting yourself setup with wxwindows and MinGW=20 would be good, because it is most similar environment to that used to=20 build for Linux and MacOSX. Also, since it's free, it might be more=20 accessible to people. Of course, it would help if we had better step-by-step directions to=20 get people set up with this. I'm hoping that as more people get it set=20= up, they can help with this. Darren "]data[" got it set up for him,=20 although he seems to have taken a slightly different route than I did. Maybe also we need to make the Makefiles, etc, a little more flexible=20 to handle different ways that people might get things set up. =20 (Already, I've seen this with MacOSX also). > The "make" for wxWindows has been running for a while now (I did not=20= > even use the Optimize option).=A0 I guess my 320 MHz Celeron is = getting=20 > slow for this type of work. naah, I have a 300Mhz PII (with just 128Mb ram!) that I'm using. More=20= memory would help when linking with wxwindows, though, but it works=20 well enough. I'm sorry that getting setup is so frustrating for now. If people do=20 it, and help with "developer docs" for it, it will get easier. Maybe=20 we can figure out a way to "script" the setup for people, so they can=20 just run some script, and it will get cygwin, MinGW, and wxwindows all=20= set up for them on windows, which will make this easier for everyone. Hang in there! > Regards, > Uriel > > -----Original Message----- > From: Steve Kann [mailto:st...@st...] > Sent: Saturday, June 14, 2003 2:36 PM > To: ur...@ad... > Cc: 'iaxclient devel' > Subject: Re: [Iaxclient-devel] iaxclient's first contributor > > > On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla wrote: > > Can we learn more as to what these new changes entail? > What I make out of it is a Microsoft-Visual-C++ version, am I correct? > Uriel > > > Yes, it is one project file to build the library with MSVC, and a new=20= > Win32 only client, with project files to build under MSVC. > > -SteveK > > > > -----Original Message----- > From: iax...@li...=20 > [mailto:iax...@li...]On Behalf Of Steve=20= > Kann > Sent: Friday, June 13, 2003 7:46 PM > To: iaxclient devel > Subject: [Iaxclient-devel] iaxclient's first contributor > > > This is just a note to thank Tili for becoming iaxclient's first=20 > contributor. > > Today, I just committed his contributions, which include some=20 > portability changes, as well as MSVC project files for the library,=20 > and a new simple Win32-only client, WinIAX. > > These are all available now in CVS.=A0 (or should be real soon,=20 > sourceforge anonymous CVS seems to be lagging a bit -- I think it's=20 > running on a backup from last night, although the developer CVS access=20= > is working). > > -SteveK > > > <image.tiff> > > > |
|
From: Uriel C. <ur...@ad...> - 2003-06-15 05:23:47
|
Steve:
I am still having problems with the /iaxclient/simpleclient/wx compile.
I installed wxWindows:
1) set up the WXWIN envronment variable to point to the root of where
wxWindows is located. (c:\Cygwin\usr\src\wxWindows)
2) edited src/make95.env to basically have MINGW32=1 and MINGW32VERSION=1
(after verifying with gcc --version).
3) executed "make -f makefile.g95" from /src/msw and from /samples/minimal.
It all seems to all have run OK. I did check that I could use the Unix
commands "cp", "mv" and "rm".
is there a way to verify that the wxWindows installed properly?
I also checked in the iaxclient/simpleclient/wx Makefile that the WXWIN
variable is pointing to a correct subdirectory that exists.
Then I went to c:Cygwin/usr/src/iaxcient/simpleclient/wx, did a "make clean"
followed by "make".
After a lot of scrolling I get the message *** error 1 in wx.o.
It is 1:15 AM so I am going to call it a quit.
Suggestions will be great!
Regards,
Uriel
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Uriel
Carrasquilla
Sent: Saturday, June 14, 2003 7:10 PM
To: 'Steve Kann'
Cc: 'iaxclient devel'
Subject: RE: [Iaxclient-devel] iaxclient's first contributor
Steve:
I am debating in my mind if I put my energy into MSVC or MinGW. I do come
from the Linux world and so far I like what I see with Cygwin (feels like
home). However, I don't want to be at a disadvantage long term and I would
seriously consider switching over to MSVC. I would be making new friends at
work with the Windows cloud.
If I was to have a Linux machine, I would not use iaxclient, I would go
for the full * (unless a Linux PDA). In my mind, iaxclient's best place is
the Mac and the Windows environments.
The "make" for wxWindows has been running for a while now (I did not even
use the Optimize option). I guess my 320 MHz Celeron is getting slow for
this type of work.
Regards,
Uriel
-----Original Message-----
From: Steve Kann [mailto:st...@st...]
Sent: Saturday, June 14, 2003 2:36 PM
To: ur...@ad...
Cc: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla wrote:
Can we learn more as to what these new changes entail?
What I make out of it is a Microsoft-Visual-C++ version, am I correct?
Uriel
Yes, it is one project file to build the library with MSVC, and a new
Win32 only client, with project files to build under MSVC.
-SteveK
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Steve Kann
Sent: Friday, June 13, 2003 7:46 PM
To: iaxclient devel
Subject: [Iaxclient-devel] iaxclient's first contributor
This is just a note to thank Tili for becoming iaxclient's first
contributor.
Today, I just committed his contributions, which include some
portability changes, as well as MSVC project files for the library, and a
new simple Win32-only client, WinIAX.
These are all available now in CVS. (or should be real soon,
sourceforge anonymous CVS seems to be lagging a bit -- I think it's running
on a backup from last night, although the developer CVS access is working).
-SteveK
<image.tiff>
|
|
From: Mark S. <mar...@di...> - 2003-06-14 22:45:07
|
Unfortunately, no, there's a lot more initialization that has to be done.
You'd pretty much need to port zaptel, or at least the portion that sets
up the device via the control URBs. Look at wcusb.c.
Mark
On Sat, 14 Jun 2003, Panny Malialis wrote:
> Hi Mark :)
>
> I hear you are in jolly old england at the moment!!!, how's it going? :)
>
> Do you have a clue as to what needs to be done in order to make my
> s100u come alive under osx so I can use it with iaxclient instead of
> the standard mic/speakers?
> I think it might just need a command to tell it to "wake up" as
> everything seems to be there driver-wise.
>
> Thanks
>
> Panny
>
>
> On Saturday, June 14, 2003, at 03:28 pm, Mark Spencer wrote:
>
> > No, it was nasty to start with and this just makes it even nastier. I
> > think the cleaner way would be to do something like this:
> >
> > struct sillystruct {
> > struct iax2_frame fr2;
> > unsigned char buffer[4096];
> > } tmp;
> >
> > and then reference tmp.fr2 and tmp.buffer;
> >
> > Mark
> >
> > On 12 Jun 2003, Steve Kann wrote:
> >
> >>
> >> Mark,
> >>
> >> Here's a good one, that took a bit to figure out also. This
> >> problem
> >> only occurs with MacOSX, although it just depends on which way the
> >> stack
> >> grows..
> >>
> >> in iax_send, you have the following code:
> >> unsigned char buffer[4096]; /* Buffer -- must
> >> preceed fr2 */
> >> struct iax_frame fr2;
> >> struct iax_frame *fr;
> >>
> >> and later, you do this:
> >> if (now) {
> >> fr = &fr2;
> >> } else
> >> fr = iax_frame_new(DIRECTION_OUTGRESS, f->datalen);
> >> if (!fr) {
> >> IAXERROR "Out of memory\n");
> >> return -1;
> >> }
> >>
> >> fprintf(stderr, "now=%d, fr=%x, &fr2=%x\n", now, fr, &fr2);
> >> fprintf(stderr, "f->datalen=%d\n", f->datalen);
> >>
> >> /* Copy our prospective frame into our immediate or
> >> retransmitted wrapper */
> >> iax_frame_wrap(fr, f);
> >>
> >> fprintf(stderr, "now=%d, fr=%x, &fr2=%x\n", now, fr, &fr2);
> >>
> >>
> >> (fprintfs are mine) which if (now=1) and f has data, copies some items
> >> from f into fr2, and then copies data to from f to fr. This data ends
> >> up past the end of fr2, which you account for, on machines with one
> >> stack direction, with the buffer on the stack.
> >>
> >> So, I think it would be better to just do this instead:
> >> double buffer[1024]; /* Buffer -- does double
> >> guarantee us proper alignment? */
> >> struct iax_frame *fr;
> >>
> >> [...]
> >>
> >> if (now) {
> >> fr = (struct iax_frame *)&buffer;
> >> } else
> >> fr = iax_frame_new(DIRECTION_OUTGRESS, f->datalen);
> >> if (!fr) {
> >> IAXERROR "Out of memory\n");
> >> return -1;
> >> }
> >>
> >> fprintf(stderr, "now=%d, fr=%x\n", now, fr);
> >> fprintf(stderr, "f->datalen=%d\n", f->datalen);
> >>
> >> /* Copy our prospective frame into our immediate or
> >> retransmitted wrapper */
> >> iax_frame_wrap(fr, f);
> >>
> >> fprintf(stderr, "now=%d, fr=%x\n", now, fr);
> >>
> >>
> >> Does this seem like it will be more portable?
> >>
> >> It works for me on MacOSX/PPC, Linux/x86, Win2K/x86.
> >>
> >> Attached also please find my current diff between my local libiax2 and
> >> digium's CVS. It is still mostly portability fixes, plus the two
> >> bugfixes (this one, and the buf[len-1] = 0 issue).
> >>
> >> Next on the list: using IAX2, for some reason the DNID isn't being
> >> honored. This is kinda strange, because using "iax2 debug" on the
> >> console of a * server, it shows the DNID properly, but I still end up
> >> in
> >> the "s" extension for the context, instead of the requested
> >> extension..
> >>
> >>
> >> -SteveK
> >>
> >>
> >>
> >>
> >> --
> >> Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 - (212)
> >> 533-1775
> >> HorizonLive.com - collaborate . interact . learn
> >> "The box said 'Requires Windows 95, NT, or better,' so I installed
> >> Linux."
> >>
> >
> >
> >
> > -------------------------------------------------------
> > This SF.NET email is sponsored by: eBay
> > Great deals on office technology -- on eBay now! Click here:
> > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> > _______________________________________________
> > Iaxclient-devel mailing list
> > Iax...@li...
> > https://lists.sourceforge.net/lists/listinfo/iaxclient-devel
> >
>
|
|
From: Uriel C. <ur...@ad...> - 2003-06-14 22:31:34
|
Steve:
I am debating in my mind if I put my energy into MSVC or MinGW. I do come
from the Linux world and so far I like what I see with Cygwin (feels like
home). However, I don't want to be at a disadvantage long term and I would
seriously consider switching over to MSVC. I would be making new friends at
work with the Windows cloud.
If I was to have a Linux machine, I would not use iaxclient, I would go for
the full * (unless a Linux PDA). In my mind, iaxclient's best place is the
Mac and the Windows environments.
The "make" for wxWindows has been running for a while now (I did not even
use the Optimize option). I guess my 320 MHz Celeron is getting slow for
this type of work.
Regards,
Uriel
-----Original Message-----
From: Steve Kann [mailto:st...@st...]
Sent: Saturday, June 14, 2003 2:36 PM
To: ur...@ad...
Cc: 'iaxclient devel'
Subject: Re: [Iaxclient-devel] iaxclient's first contributor
On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla wrote:
Can we learn more as to what these new changes entail?
What I make out of it is a Microsoft-Visual-C++ version, am I correct?
Uriel
Yes, it is one project file to build the library with MSVC, and a new
Win32 only client, with project files to build under MSVC.
-SteveK
-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of Steve Kann
Sent: Friday, June 13, 2003 7:46 PM
To: iaxclient devel
Subject: [Iaxclient-devel] iaxclient's first contributor
This is just a note to thank Tili for becoming iaxclient's first
contributor.
Today, I just committed his contributions, which include some
portability changes, as well as MSVC project files for the library, and a
new simple Win32-only client, WinIAX.
These are all available now in CVS. (or should be real soon,
sourceforge anonymous CVS seems to be lagging a bit -- I think it's running
on a backup from last night, although the developer CVS access is working).
-SteveK
<image.tiff>
|
|
From: Steve K. <st...@st...> - 2003-06-14 18:34:55
|
On Saturday, June 14, 2003, at 02:56 AM, Uriel Carrasquilla wrote: > Can we learn more as to what these new changes entail? > What I make out of it is a Microsoft-Visual-C++ version, am I correct? > Uriel > Yes, it is one project file to build the library with MSVC, and a new=20 Win32 only client, with project files to build under MSVC. -SteveK > -----Original Message----- > From: iax...@li...=20 > [mailto:iax...@li...]On Behalf Of Steve=20= > Kann > Sent: Friday, June 13, 2003 7:46 PM > To: iaxclient devel > Subject: [Iaxclient-devel] iaxclient's first contributor > > > This is just a note to thank Tili for becoming iaxclient's first=20 > contributor. > > Today, I just committed his contributions, which include some=20 > portability changes, as well as MSVC project files for the library,=20 > and a new simple Win32-only client, WinIAX. > > These are all available now in CVS.=A0 (or should be real soon,=20 > sourceforge anonymous CVS seems to be lagging a bit -- I think it's=20 > running on a backup from last night, although the developer CVS access=20= > is working). > > -SteveK > > <image.tiff> > > |
|
From: Steve K. <st...@st...> - 2003-06-14 18:33:23
|
Panny, Interesting, 'cause I only have one file there :) The file you need copied, on my machine is called = libwx_mac-2.4.rsrc. =20 I used the wildcard, because I figured it would let things work with=20 different versions of wxWindows installed. I guess I need to figure=20 out something smarter for that. Maybe you have two versions of wxwindows installed? Anyway, = I'll look=20 into making the Makefile a bit smarter about this (perhaps doing=20 something with wx-config --rezflags), but for now, you can probably=20 just change the Makefile to copy libwx_mac-2.4.rsrc (or whatever=20 version of the resource you need) to wx.rsrc, and that should be OK for=20= you to build now. -SteveK On Saturday, June 14, 2003, at 10:51 AM, Panny Malialis wrote: > Hello, > > I re-compiled the vxwindows on the ibook with --enable-debug and=20 > --disable shared > > Now when I compile wx, i get the following: > > [maccy:iaxclient/simpleclient/wx] panny# make > (cd ../../lib; make libiaxclient.a) > make[1]: `libiaxclient.a' is up to date. > `wx-config --cxx` -I../../lib -I../../lib/libiax/src=20 > -I../../lib/gsm/inc -I../../lib/portaudio/pa_common=20 > -I../../lib/portaudio/pablio -Iinclude -g -DPOSIXSLEEP `wx-config=20 > --cflags` -c -o wx.o wx.cc > mkdir -p wx.app/Contents/MacOS wx.app/Contents/Resources > cp `wx-config --prefix`/lib/libwx_mac*.rsrc=20 > wx.app/Contents/Resources/wx.rsrc > cp: copying multiple files, but last argument=20 > `wx.app/Contents/Resources/wx.rsrc' is not a directory > Try `cp --help' for more information. > make: *** [wx.app] Error 1 > > > Any thoughts ? > > Thanks > > Panny > > > On Friday, June 13, 2003, at 03:16 pm, Darren Smith wrote: > >> Hi all >> =A0 >> I found when i installed wxwindows, i had to use --enable-debug as=20 >> well on the commandline as well as the --disable-shared i think it=20 >> was, to force it to create a static library. >> =A0 >> It'll then=A0create a debug .a file in the wxwindows/lib dir=20 >> libwxs<something>d-4.2.0.a , can't remember the exact filename (i'm=20= >> 120 miles from my pc at home atm) anyway, i had to rename it to=20 >> remove the -4.2.0 bit for it to work. >> =A0 >> Also, when you set the WXWIN variable, use=20 >> /c:/<windows-path-to-wxwindows-dir> instead of the cygwin path, as=20 >> mingw wont be able to find it. >> =A0 >> PS. Great work on the winiax client Faizan, looks nice in the quick=20= >> test i gave it from my laptop :-) >> =A0 >> Best Regards >> =A0 >> Darren ']data[' Smith >> Game Digital Ltd >> =A0 >> >> ----- Original Message ----- >> From: Steve Kann >> To: ur...@ad... >> Cc: 'iaxclient devel' >> Sent: Friday, June 13, 2003 3:04 PM >> Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32=20= >> Latency >> >> On Thu, 2003-06-12 at 23:12, Uriel Carrasquilla wrote: >> >> Steve: >> Right on!=A0 My next step is to install wxwindows from=20 >> www.wxwindows.org=A0as per your instructions with MinGW.=A0 I think I = am=20 >> going to call it a day but either tomorrow or Saturday I will get to=20= >> it. >> I am also going to play with the settings in portaudio and will let=20= >> the list know what worked for me.=A0 I will document the steps to get=20= >> everything up and running on a Windows XP environment so we can put=20= >> it in a README-WIN.txt file. >> Thank you for your invaluable support, without you I would have not=20= >> made it this far. >> >> >> >> Great!=A0 I'm glad I could help, and I'm glad you stuck it out. >> >> While I think it's a bit harder to get set up with MinGW and=20 >> wxwindows, that it would be to use VC (once Faizan's project files=20 >> are in place, etc), I think it's better, because then changes and=20 >> contributions you make are helpful for people on platforms other than=20= >> Windows. >> >> Bill still doesn't have 100% of the market yet! >> >> -SteveK >> >> >> >> Regards, >> Uriel >> >> -----Original Message----- >> From: Steve Kann [mailto:st...@st...] >> Sent: Thursday, June 12, 2003 9:37 AM >> To: ur...@ad... >> Cc: 'iaxclient devel' >> Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32=20= >> Latency >> >> >> On Wed, 2003-06-11 at 22:41, Uriel Carrasquilla wrote: >> >> Steve: >> It is now working with the "make" from Cygwin.=A0 I had to download = it=20 >> from http://cygwin.com/setup.exe as it is not part of the default=20 >> install. >> I was able to compile with "make clena" followed by "make" under=20 >> iaxclient/simpleclient/testcall.=A0 It works and I tested it and=20 >> modified it to use my own *.=A0 There was quite a bit of noise and=20 >> quite a bit of delay but it is very promissing. >> >> >> Cool.=A0 I'm glad you got it working.=A0 I guess I installed cygwin a=20= >> long time ago, and I probably did install more than the default=20 >> install, so we should note this in the README with the sources. >> >> Thanks for sticking in there! >> >> The latency can be adjusted somewhat by setting an environment=20 >> variable, PA_MIN_LATENCY_MSEC=A0 It defaults to 200ms for Win9x, and=20= >> 400ms for NT.=A0 Try setting it to something smaller, and it might = work=20 >> for you.=A0 Some people have tried setting this to 50ms or so, with=20= >> success, but it depends on your system. >> >> The portaudio people set this by default pretty high on windows,=20 >> because windows has pretty bad real-time support.=A0 It's better, by=20= >> default, on Linux/MacOSX. >> >> All of this is really in the portaudio library code, so if you're=20 >> looking to change things or research them, look in the portaudio=20 >> directory, and/or the portaudio website and mailing lists -- there's=20= >> lots of info on it there, and I think they're improving things for=20 >> their next release. >> >> >> Then I got ambitious and tried the same steps undex=20 >> iaxclient/simpleclient/wx.=A0 I watched in horror the screen go for=20= >> quite a while.=A0 Then it stopped with a message "1 error in wx.o".=A0 = I=20 >> tried to redirect the output to file so I could attach it here but=20 >> only got the first few lines of the "Makefile" execution.=A0 Then, = when=20 >> the Cygwin make takes over, it all went back to the STD output, my=20 >> screen. >> Since I made it this far, I am now more committed than ever. >> Did I miss a step to compile the "GUI" version? >> >> >> And if you thought getting the environment setup for compiling=20 >> "testcall" was complicated, wait till you try compiling with=20 >> wxwindows :)=A0 (OK, it's not _too_ bad, really.=A0 Several people=20 >> besides me have done this already). >> >> Basically, what you need to do is get wxwindows from wxwindows.org,=20= >> compile that with mingw (when you do this, make sure you compile it=20= >> to make _static libraries_, not DLLs), and then if you have the WXWIN=20= >> environment variable set properly, the build of wx will succeed. >> >> The errors you got are all probably because you don't have wxwin=20 >> installed/compiled, so it can't find the wxwin headers, and then the=20= >> compiler can't make sense out of the rest of the code. >> >> -SteveK >> >> >> Regards, >> Uriel >> > <image.tiff> >> >> > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: eBay > Great deals on office technology -- on eBay now! Click here: > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Iaxclient-devel mailing list > Iax...@li... > https://lists.sourceforge.net/lists/listinfo/iaxclient-devel > |
|
From: Panny M. <pa...@ho...> - 2003-06-14 15:03:53
|
Hi Mark :)
I hear you are in jolly old england at the moment!!!, how's it going? :)
Do you have a clue as to what needs to be done in order to make my
s100u come alive under osx so I can use it with iaxclient instead of
the standard mic/speakers?
I think it might just need a command to tell it to "wake up" as
everything seems to be there driver-wise.
Thanks
Panny
On Saturday, June 14, 2003, at 03:28 pm, Mark Spencer wrote:
> No, it was nasty to start with and this just makes it even nastier. I
> think the cleaner way would be to do something like this:
>
> struct sillystruct {
> struct iax2_frame fr2;
> unsigned char buffer[4096];
> } tmp;
>
> and then reference tmp.fr2 and tmp.buffer;
>
> Mark
>
> On 12 Jun 2003, Steve Kann wrote:
>
>>
>> Mark,
>>
>> Here's a good one, that took a bit to figure out also. This
>> problem
>> only occurs with MacOSX, although it just depends on which way the
>> stack
>> grows..
>>
>> in iax_send, you have the following code:
>> unsigned char buffer[4096]; /* Buffer -- must
>> preceed fr2 */
>> struct iax_frame fr2;
>> struct iax_frame *fr;
>>
>> and later, you do this:
>> if (now) {
>> fr = &fr2;
>> } else
>> fr = iax_frame_new(DIRECTION_OUTGRESS, f->datalen);
>> if (!fr) {
>> IAXERROR "Out of memory\n");
>> return -1;
>> }
>>
>> fprintf(stderr, "now=%d, fr=%x, &fr2=%x\n", now, fr, &fr2);
>> fprintf(stderr, "f->datalen=%d\n", f->datalen);
>>
>> /* Copy our prospective frame into our immediate or
>> retransmitted wrapper */
>> iax_frame_wrap(fr, f);
>>
>> fprintf(stderr, "now=%d, fr=%x, &fr2=%x\n", now, fr, &fr2);
>>
>>
>> (fprintfs are mine) which if (now=1) and f has data, copies some items
>> from f into fr2, and then copies data to from f to fr. This data ends
>> up past the end of fr2, which you account for, on machines with one
>> stack direction, with the buffer on the stack.
>>
>> So, I think it would be better to just do this instead:
>> double buffer[1024]; /* Buffer -- does double
>> guarantee us proper alignment? */
>> struct iax_frame *fr;
>>
>> [...]
>>
>> if (now) {
>> fr = (struct iax_frame *)&buffer;
>> } else
>> fr = iax_frame_new(DIRECTION_OUTGRESS, f->datalen);
>> if (!fr) {
>> IAXERROR "Out of memory\n");
>> return -1;
>> }
>>
>> fprintf(stderr, "now=%d, fr=%x\n", now, fr);
>> fprintf(stderr, "f->datalen=%d\n", f->datalen);
>>
>> /* Copy our prospective frame into our immediate or
>> retransmitted wrapper */
>> iax_frame_wrap(fr, f);
>>
>> fprintf(stderr, "now=%d, fr=%x\n", now, fr);
>>
>>
>> Does this seem like it will be more portable?
>>
>> It works for me on MacOSX/PPC, Linux/x86, Win2K/x86.
>>
>> Attached also please find my current diff between my local libiax2 and
>> digium's CVS. It is still mostly portability fixes, plus the two
>> bugfixes (this one, and the buf[len-1] = 0 issue).
>>
>> Next on the list: using IAX2, for some reason the DNID isn't being
>> honored. This is kinda strange, because using "iax2 debug" on the
>> console of a * server, it shows the DNID properly, but I still end up
>> in
>> the "s" extension for the context, instead of the requested
>> extension..
>>
>>
>> -SteveK
>>
>>
>>
>>
>> --
>> Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 - (212)
>> 533-1775
>> HorizonLive.com - collaborate . interact . learn
>> "The box said 'Requires Windows 95, NT, or better,' so I installed
>> Linux."
>>
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: eBay
> Great deals on office technology -- on eBay now! Click here:
> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> _______________________________________________
> Iaxclient-devel mailing list
> Iax...@li...
> https://lists.sourceforge.net/lists/listinfo/iaxclient-devel
>
|
|
From: Panny M. <pa...@ho...> - 2003-06-14 14:50:32
|
Hello, I re-compiled the vxwindows on the ibook with --enable-debug and=20 --disable shared Now when I compile wx, i get the following: [maccy:iaxclient/simpleclient/wx] panny# make (cd ../../lib; make libiaxclient.a) make[1]: `libiaxclient.a' is up to date. `wx-config --cxx` -I../../lib -I../../lib/libiax/src=20 -I../../lib/gsm/inc -I../../lib/portaudio/pa_common=20 -I../../lib/portaudio/pablio -Iinclude -g -DPOSIXSLEEP `wx-config=20 --cflags` -c -o wx.o wx.cc mkdir -p wx.app/Contents/MacOS wx.app/Contents/Resources cp `wx-config --prefix`/lib/libwx_mac*.rsrc=20 wx.app/Contents/Resources/wx.rsrc cp: copying multiple files, but last argument=20 `wx.app/Contents/Resources/wx.rsrc' is not a directory Try `cp --help' for more information. make: *** [wx.app] Error 1 Any thoughts ? Thanks Panny On Friday, June 13, 2003, at 03:16 pm, Darren Smith wrote: > Hi all > =A0 > I found when i installed wxwindows, i had to use --enable-debug as=20 > well on the commandline as well as the --disable-shared i think it=20 > was, to force it to create a static library. > =A0 > It'll then=A0create a debug .a file in the wxwindows/lib dir=20 > libwxs<something>d-4.2.0.a , can't remember the exact filename (i'm=20 > 120 miles from my pc at home atm) anyway, i had to rename it to remove=20= > the -4.2.0 bit for it to work. > =A0 > Also, when you set the WXWIN variable, use=20 > /c:/<windows-path-to-wxwindows-dir> instead of the cygwin path, as=20 > mingw wont be able to find it. > =A0 > PS. Great work on the winiax client Faizan, looks nice in the quick=20 > test i gave it from my laptop :-) > =A0 > Best Regards > =A0 > Darren ']data[' Smith > Game Digital Ltd > =A0 > > ----- Original Message ----- > From: Steve Kann > To: ur...@ad... > Cc: 'iaxclient devel' > Sent: Friday, June 13, 2003 3:04 PM > Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32=20= > Latency > > On Thu, 2003-06-12 at 23:12, Uriel Carrasquilla wrote: > > Steve: > Right on!=A0 My next step is to install wxwindows from=20 > www.wxwindows.org=A0as per your instructions with MinGW.=A0 I think I = am=20 > going to call it a day but either tomorrow or Saturday I will get to=20= > it. > I am also going to play with the settings in portaudio and will let=20 > the list know what worked for me.=A0 I will document the steps to get=20= > everything up and running on a Windows XP environment so we can put it=20= > in a README-WIN.txt file. > Thank you for your invaluable support, without you I would have not=20 > made it this far. > > > > Great!=A0 I'm glad I could help, and I'm glad you stuck it out. > > While I think it's a bit harder to get set up with MinGW and=20 > wxwindows, that it would be to use VC (once Faizan's project files are=20= > in place, etc), I think it's better, because then changes and=20 > contributions you make are helpful for people on platforms other than=20= > Windows. > > Bill still doesn't have 100% of the market yet! > > -SteveK > > > > Regards, > Uriel > > -----Original Message----- > From: Steve Kann [mailto:st...@st...] > Sent: Thursday, June 12, 2003 9:37 AM > To: ur...@ad... > Cc: 'iaxclient devel' > Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32=20= > Latency > > > On Wed, 2003-06-11 at 22:41, Uriel Carrasquilla wrote: > > Steve: > It is now working with the "make" from Cygwin.=A0 I had to download it=20= > from http://cygwin.com/setup.exe as it is not part of the default=20 > install. > I was able to compile with "make clena" followed by "make" under=20 > iaxclient/simpleclient/testcall.=A0 It works and I tested it and=20 > modified it to use my own *.=A0 There was quite a bit of noise and = quite=20 > a bit of delay but it is very promissing. > > > Cool.=A0 I'm glad you got it working.=A0 I guess I installed cygwin a = long=20 > time ago, and I probably did install more than the default install, so=20= > we should note this in the README with the sources. > > Thanks for sticking in there! > > The latency can be adjusted somewhat by setting an environment=20 > variable, PA_MIN_LATENCY_MSEC=A0 It defaults to 200ms for Win9x, and=20= > 400ms for NT.=A0 Try setting it to something smaller, and it might = work=20 > for you.=A0 Some people have tried setting this to 50ms or so, with=20 > success, but it depends on your system. > > The portaudio people set this by default pretty high on windows,=20 > because windows has pretty bad real-time support.=A0 It's better, by=20= > default, on Linux/MacOSX. > > All of this is really in the portaudio library code, so if you're=20 > looking to change things or research them, look in the portaudio=20 > directory, and/or the portaudio website and mailing lists -- there's=20= > lots of info on it there, and I think they're improving things for=20 > their next release. > > > Then I got ambitious and tried the same steps undex=20 > iaxclient/simpleclient/wx.=A0 I watched in horror the screen go for=20 > quite a while.=A0 Then it stopped with a message "1 error in wx.o".=A0 = I=20 > tried to redirect the output to file so I could attach it here but=20 > only got the first few lines of the "Makefile" execution.=A0 Then, = when=20 > the Cygwin make takes over, it all went back to the STD output, my=20 > screen. > Since I made it this far, I am now more committed than ever. > Did I miss a step to compile the "GUI" version? > > > And if you thought getting the environment setup for compiling=20 > "testcall" was complicated, wait till you try compiling with wxwindows=20= > :)=A0 (OK, it's not _too_ bad, really.=A0 Several people besides me = have=20 > done this already). > > Basically, what you need to do is get wxwindows from wxwindows.org,=20 > compile that with mingw (when you do this, make sure you compile it to=20= > make _static libraries_, not DLLs), and then if you have the WXWIN=20 > environment variable set properly, the build of wx will succeed. > > The errors you got are all probably because you don't have wxwin=20 > installed/compiled, so it can't find the wxwin headers, and then the=20= > compiler can't make sense out of the rest of the code. > > -SteveK > > > Regards, > Uriel > <image.tiff> > > |
72 messages has been excluded from this view by a project administrator.
