RE: [Iaxclient-devel] iaxclient wxWindows MinGW compile

[Uriel C. <ur...@ad...>]

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>