|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [CRONOLOG]: Cronolog 1.6.2 for WIndows - Compile Success without Cygwin dependency
- To: <cronolog-users@xxxxxxxxxxxxxxxx>
- Subject: RE: [CRONOLOG]: Cronolog 1.6.2 for WIndows - Compile Success without Cygwin dependency
- From: "Ian Huynh" <ianh@xxxxxxxxxxx>
- Date: Fri, 17 Sep 2004 14:49:55 -0700
- Thread-index: AcScge5vDTUs7/QyTxSyTDNnaUPgKwARkInAAA3xWuA=
- Thread-topic: [CRONOLOG]: Cronolog 1.6.2 for WIndows - Compile Success without Cygwin dependency
Jim
That was it. Recompiling without -g yielded a 40K binary.
>-----Original Message-----
>From: owner-cronolog-users@xxxxxxxxxxxxxxxx
>[mailto:owner-cronolog-users@xxxxxxxxxxxxxxxx]On Behalf Of Ian Huynh
>Sent: Friday, September 17, 2004 8:19 AM
>To: cronolog-users@xxxxxxxxxxxxxxxx
>Subject: RE: [CRONOLOG]: Cronolog 1.6.2 for WIndows - Compile Success
>without Cygwin dependency
>
>
>Jim
>Thanks for the heads-up. I just notice the default generated
>makefile was calling gcc -g.
>
>One more question.. using statically linked lib in this mode
>in win32 (ie. apache spawning separate processes
>for each cronolog), am i wasting a lot of memory if I am
>creating a few dozen log files in apache?
>Ian.
>
>
>>-----Original Message-----
>>From: jim.r.halfpenny@xxxxxxxxxxxxxxxxxx
>>[mailto:jim.r.halfpenny@xxxxxxxxxxxxxxxxxx]
>>Sent: Thursday, September 16, 2004 11:45 PM
>>To: Ian Huynh
>>Cc: cronolog-users@xxxxxxxxxxxxxxxx
>>Subject: RE: [CRONOLOG]: Cronolog 1.6.2 for WIndows - Compile Success
>>without Cygwin dependency
>>
>>
>>Hi,
>>I imagine one the larger either contains debugging symbols or
>>is statically
>>linked. A statically linked binary is a good idea if you want
>>your build to
>>be portable across different windows boxes and avoid the problems of
>>missing libraries.
>>
>>Cheers,
>>Jim
>>
>>
>>
>>
>>
>>"Ian Huynh" <ianh@xxxxxxxxxxx>@ford-mason.co.uk on 16/09/2004 22:37:34
>>
>>Sent by: owner-cronolog-users@xxxxxxxxxxxxxxxx
>>
>>
>>To: cronolog-users
>>cc:
>>bcc:
>>Subject: RE: [CRONOLOG]: Cronolog 1.6.2 for WIndows -
>>Compile Success
>> without Cygwin dependency
>>
>>
>>One curious thing. The newly compiled 1.6.2 binary is 420K
>>while the 1.6.1
>>binary is only 64K..?
>>
>>
>>
>>
>>>-----Original Message-----
>>>From: Ian Huynh
>>>Sent: Thursday, September 16, 2004 2:12 PM
>>>To: cronolog-users@xxxxxxxxxxxxxxxx
>>>Subject: RE: [CRONOLOG]: Cronolog 1.6.2 for WIndows - Compile Success
>>>without Cygwin dependency
>>>
>>>
>>>I think I finally have a compiled binary for Cronolog 1.6.2
>>>for Win2K that does not depend on Cygwin1.dll. The process
>>>was a bit convoluted and so here's the instructions just in
>>>case someone wants to do the same. Hopefully this will be
>>>useful to someone else.
>>>
>>>(Note: The standard source from 1.6.2 builds fine with Cygwin
>>>but during execution, it requires Cygwin1.dll to be present in
>>>the path.)
>>>
>>>The attached files are as follows:
>>>
>>>1. howToCompileChronolog1.6.2ForWin2K.htm - instructions on
>>>how to build, incl. errors that I have encountered and what I
>>>did to get around the error.
>>>2. cronolog-1.6.2.windows.build.zip - a zip copy of my build
>>>directory. You can find the .exe in cronolog-1.6.2\src directory
>>>3. a diff of cronoutils.c in html format
>>>
>>>Of importance is item (3). I had to modify 1 line in
>>>cronoutils.c when compiling. I think I am right but not sure
>>>if this is correct. It
>>>seems to compile and runs OK.
>>>
>>>
>>>To view the attached HTML files, you are going to need either
>>>IE or FireFox to view them properly)
>>>
>>>AND, as a disclaimer, this stuff hasn't been tested !
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Matthew Grosso [mailto:mgrosso@xxxxxxxxxxxxx]
>>>>Sent: Thursday, September 16, 2004 9:34 AM
>>>>To: Ian Huynh
>>>>Cc: cronolog-users@xxxxxxxxxxxxxxxx
>>>>Subject: Re: [CRONOLOG]: Cronolog 1.6.2 for WIndows
>>>>
>>>>
>>>>
>>>>Ian,
>>>>
>>>>You might want to try MinGW. Its basically cygwin minus the
>>>>compatibility layer
>>>>dll. Not all of the the posix functions are there, but
>>>>cronolog is pretty
>>>>small, so there's a good chance it will still compile, and if
>>>>not ifdefing the
>>>>missing functionality shouldnt be too hard. http://www.mingw.org
>>>>
>>>>Matt
>>>>
>>>>On Sep 13 0923, Ian Huynh wrote:
>>>>> Andrew
>>>>> Thanks. It does work with Cygwin out of the box but the
>>>>.exe has a dependency on cygwin1.dll which
>>>>> is not desirable
>>>>>
>>>>> I've tried to use GCC option -mno-cygwin but that created a
>>>>whole set of other problems with missing header file (e.g.
>>langinfo.h)
>>>>>
>>>>> Ian.
>>>>>
>>>>>
>>>>> >-----Original Message-----
>>>>> >From: Andrew Ford [mailto:A.Ford@xxxxxxxxxxxxxxxx]
>>>>> >Sent: Saturday, September 11, 2004 11:39 PM
>>>>> >To: Ian Huynh; cronolog-users@xxxxxxxxxxxxxxxx
>>>>> >Subject: Re: [CRONOLOG]: Cronolog 1.6.2 for WIndows
>>>>> >
>>>>> >
>>>>> >Ian Huynh wrote:
>>>>> >
>>>>> >>
>>>>> >>Will there be a 1.6.2 build for Win2K? If not, are there
>>>>> >>instructions on how to build for Win2K ?
>>>>> >>Thanks.
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >I don't do the builds for Windows, and don't actually know
>>>>how to --
>>>>> >although I suspect that cronolog, like many programs designed for
>>>>> >Unix-like operating systems, would compile
>straightforwardly under
>>>>> >Cygwin on Windows. The existing Windows version was
>>>>contributed. If
>>>>> >someone contributes a Windows build of a newer version I will
>>>>> >put it up too.
>>>>> >
>>>>> >Andrew
>>>>> >
>>>>> >--
>>>>> >Andrew Ford, Director Pauntley Prints / Ford & Mason Ltd
>>>>> >A.Ford@xxxxxxxxxxxxxxxx South Wing Compton House
>>>>> >pauntley-prints.co.uk Compton Green, Redmarley Tel: +44
>>>>> >1531 829900
>>>>> >ford-mason.co.uk Gloucester GL19 3JB Fax: +44
>>>>> >1531 829901
>>>>> >refcards.com/cronolog.org Great Britain Mobile: +44
>>>>> >7785 258278
>>>>> >
>>>>> >
>>>>>
>>>>>
>>>---------------------------------------------------------------------
>>>>> cronolog-users mailing list
>>>>> --------------------------
>>>>> Send messages to "cronolog-users@xxxxxxxxxxxxxxxx"
>>>>> To unsubscribe send email to "majordomo@xxxxxxxxxxxxxxxx"
>>>>with the command:
>>>>> "unsubscribe cronolog-users"
>>>>> in the body of the message.
>>>>
>>>>--
>>>>##############################################################
>>>#########
>>>># Matt Grosso mgrosso@xxxxxxxxxxxxx w(201)963-2024
>>>c(201)780-9592 #
>>>># pgp public key is at
>>http://www.falconweb.com/~mattg/publickey.pgp #
>>>##############################################################
>>#########
>>>
>>
>>---------------------------------------------------------------------
>>cronolog-users mailing list
>>--------------------------
>>Send messages to "cronolog-users@xxxxxxxxxxxxxxxx"
>>To unsubscribe send email to "majordomo@xxxxxxxxxxxxxxxx" with
>>the command:
>>"unsubscribe cronolog-users"
>> in the body of the message.
>>
>>
>>
>>
>>
>>
>>
>
>---------------------------------------------------------------------
>cronolog-users mailing list
>--------------------------
>Send messages to "cronolog-users@xxxxxxxxxxxxxxxx"
>To unsubscribe send email to "majordomo@xxxxxxxxxxxxxxxx" with
>the command:
>"unsubscribe cronolog-users"
>in the body of the message.
>
|