So, yesterday I was working on updating our grep (we have some windows
port of grep 2.0, which predates version control, and the latest is
2.9), and it was an exceedingly weird process.
This is partly because I chose, for some crazy reason, to do it in
visual studio, which I'm sure the grep develo
> 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
>> 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
I think we should make it a policy to never convert other projects'
revision control to git, if they're not already git, because the extra
software it requires packagers to learn, install, and use does not
convey any extra benefits. (And I REALLY don't want to have to install
bzr or hg or perforce
Whoops, forgot to include the list just now. Sorry for the confusion.
> How do I do it?
I've explained this in my previous post, and you appear to have
understood. If there's something still unclear, please let me know.
>> (And I REALLY don't want to have to install
>> bzr or hg or perforce on m
> Simply put, I think we need to achieve something like this:
>
> http://happygiraffe.net/blog/files/wordpress_vendor_branch.png
Brilliant. That picture sums up what I mean exactly.
___
Mailing list: https://launchpad.net/~coapp-developers
Post to :
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
I've come up with a list of things that I try to do when shallow
forking and that I think are the "officially endorsed" or failing that
"correct" way of doing things. I'm not sure where it properly belongs,
and maybe some people wouldn't agree on all of these. Also, maybe some
of you have things to
It seems I totally forgot to check the license on gnulib. The
licensing situation is quite weird. Apparently, each gnulib "module"
is licensed individually, and that license is determined by a file in
the modules/ directory, not by the source file headers (which usually
say GPL). Most of these modu
Sounds useful.
Can these .user files be used to override defines in existing files?
Do they apply to imported files as well?
___
Mailing list: https://launchpad.net/~coapp-developers
Post to : coapp-developers@lists.launchpad.net
Unsubscribe : https
SDL_image has the ability to load image libraries like libpng and
libjpeg on demand, using a preprocessor define (e.g. LOAD_PNG_DYNAMIC)
indicating the dll filename to load. This functionality is not
required (it can link these libraries normally), and I've opted to
ignore it for now.
Do we want t
> I'm probably misunderstanding how this works, but why can't libpng for
> example, be an optional dependency for the SDL package?
It could, if I built it with dynamic loading and if nuget supported
optional dependencies. I'm just not sure if the dynamic loading has
enough advantages in practice t
12 matches
Mail list logo
