W3C home > Mailing lists > Public > uri@w3.org > February 2008

Re: uriparser 0.6.2 released

From: Sebastian Pipping <webmaster@hartwork.org>
Date: Sat, 09 Feb 2008 16:26:53 +0100
Message-ID: <47ADC63D.4080002@hartwork.org>
To: "Michael A. Puls II" <shadow2531@gmail.com>
CC: uriparser-devel@lists.sourceforge.net, uri@w3.org

Michael A. Puls II wrote:
> After converting the indents to tabs for the attachment, the makefile
> does indeed work in the win32/mingw directory.

Hm, could it be you copy-pasted from the mail instead of
saving the attachment? The file did contain tabs for indentation.

> However, would it be
> better to have the .o files written somewhere else like in
> "mingw/.objs/lib" similar to how code blocks does it when you load and
> build the uriparser project.?

Would be an option.

> Also, having the makefile build the tests or a separate makefile build
> the tests would be cool too.

I agree.

> Also, I did try to use MSYS and do ./configure, but I got a sed error.
> Is it supposed to work with MSYS?

No sure, I don't use MSYS.

> Also, I noticed that when building UriNormalize.c, there are some
> warnings in uriFixPercentEncodingInplaceA. Are those O.K. You should
> see the warnings when you build?

Just lack of time, will take care of that later.

> Also, with the mingw makefile, did you check to see if the produced
> liburiparser.a is correct? Does it have to be done statically using
> "ar" like the following instead?

I did not try, no. I let Code::Blocks or libtool take care of that
usually. I think ar should be the one, for now you just have to try.

> Should the makefile give an option to produce release and debug
> versions and shared and static versions etc.?

Yes, why not. The thing is I have to manually sync file
lists at several places (Makefile.am, Code::Blocks, Visual Studio)
So I'm not really looking for an increase of that list.
Also I use Automake to not have to write Makefiles by hand.
So that's why I originally asked you to either use Code::Blocks
or help with maintenance.

> Also, what flags can be passed when compiling? Any unicode flags?

Building uriparser should produce Ansi and Unicode code at the
same time regardless of any Unicode defines.

>> Are you interested in adding support for make check
>> and co-maintain the Makefile in the future? If so please
>> tell me your nick on SourceForge so I can add you to the
>> project.
> If I can figure things out, will let you know. I want to mess with the
> parser first. I don't know how to use it at all yet.

Sorry, tutorials on usage are still to come. For now
looking at the test suite or in libSpiff Code is your
best source besides talking to me.

> For starters, I want to figure out how to just pass in a URI and get
> the different parts. Have an example of that? (I see the doc
> directory. Do I have to build the documentation too?)

You don't necessarily have to build it as it's online at

Currently to parse a URI you have code like this:

    UriParserStateA state;
    UriUriA uri;
    state.uri = &uri;
    if (uriParseUriA(&state, "file:///home/user/song.mp3") != URI_SUCCESS) {
    	/* FAILURE */
    /* DO STUFF */

Received on Saturday, 9 February 2008 15:27:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:12 UTC