: coapp-developers@lists.launchpad.net
Subject: Re: [Coapp-developers] I think we'll want to fork gnulib
Just FYI, I've pushed a gnulib fork and a single project using it, tinycdb.
Actually, tinycdb only needs this for one function, getopt, and only
in cdb.exe, not libcdb.dll.
I had t
Just FYI, I've pushed a gnulib fork and a single project using it, tinycdb.
Actually, tinycdb only needs this for one function, getopt, and only
in cdb.exe, not libcdb.dll.
I had to make the following changes to make this work:
* Add gnulib\lib to the cdb project include path.
* Manually create
>> The two things that spring to mind here:
>> * Library A needs work to make it good for us. Library A is then updated -
>> what work do we need to do keep pace with mainline?
>
> Glare at it sternly.
>
> Honestly most of the work in these cases gets put on setting up the
> build system around whi
On Wed, Sep 28, 2011 at 1:55 AM, Adam Baxter wrote:
> Do you end up with an #ifdef soup with this approach?
> The two things that spring to mind here:
> * Library A needs work to make it good for us. Library A is then updated -
> what work do we need to do keep pace with mainline?
Glare at it
Do you end up with an #ifdef soup with this approach?
The two things that spring to mind here:
* Library A needs work to make it good for us. Library A is then updated -
what work do we need to do keep pace with mainline?
* Do we try to get Windows specific patches integrated back upstream at any
On Tue, Sep 27, 2011 at 7:52 AM, Garrett Serack wrote:
> We'd *love* to have you back in action Ted!
>
> Even just a bit of code here or there would go a long way :)
Ok, I'll do it. I guess it starts with getting back in communication :)
--
Ted Bullock
___
l.com; coapp-developers@lists.launchpad.net
Subject: Re: [Coapp-developers] I think we'll want to fork gnulib
Boy,
I keep looking in on this project and thinking I need to make time
(somehow?) in my schedule to commit.
Sheesh,
Anyway, fork it and fix it is the right answer.
On Mon, Sep 26, 20
t; To: madewokh...@gmail.com
> Cc: coapp-developers@lists.launchpad.net
> Subject: Re: [Coapp-developers] I think we'll want to fork gnulib
>
>> I think that depends on how far we're willing to go to avoid modifications
>> to the original source.
>>
>> If we
Err, not sure how I mashed my signature there...
On Mon, Sep 26, 2011 at 10:35 PM, Adam Baxter wrote:
> I think that depends on how far we're willing to go to avoid modifications
>> to the original source.
>
> If we tried to provide grep with the failure code it expects, I think
>
> that would b
>
> I think that depends on how far we're willing to go to avoid modifications
> to the original source.
If we tried to provide grep with the failure code it expects, I think
that would bring us into compatibility layer territory. Instead, we
should just accept that that's how windows works and
> Sounds interesting from a porting point of view, but are we setting
> ourselves up for a situation a-la Cygwin where we've got a modified
> "layer" sitting underneath our apps?
I think that depends on how far we're willing to go to avoid
modifications to the original source.
The grep I have bui
Sounds interesting from a porting point of view, but are we setting
ourselves up for a situation a-la Cygwin where we've got a modified
"layer" sitting underneath our apps?
--Adam
___
Mailing list: https://launchpad.net/~coapp-developers
Post to : c
12 matches
Mail list logo
