Something went wrong with this discussion, I'll quickly thank Richard for the answer.
Best Regards On Mon, Aug 18, 2014 at 2:03 PM, olivier BOURQUARD <m...@bqd.fr> wrote: > hi . > please. > I do not think you answer to my mail. > no problem. > > is the moment, my problem is : cross-compiling with sqlite.c, .h etc.... > > with Eclipse LUNA on Windows XP for Raspberry debian. > > I need to understand what is happening. > > to understand, i go to your site at the adress > www.sqlite.org/howtocompile.html > > I downloaded 'amalgamation 3080500.zip' > > at the last time , i test to compile with Eclipse ===> please see the > bmpfiles... > > one time, with -lsqlite3 in the toolchain == problem "not find" > second time, without -lsqlite3 == problem "dlsym" > > please, ave you an explanation ? > one tutorial (eventuali on eclipse) ? > > thanks. > > olivier BOURQUARD. > > i subcrib to your site. > > nb : i kan send you my "VirtualBoxe". > > > Le 18/08/2014 14:18, Richard Hipp a écrit : > >> On Sun, Aug 17, 2014 at 2:28 PM, Andrea Giammarchi < >> andrea.giammar...@gmail.com> wrote: >> >> I wonder if this is meant to be or not, it seems that starting from >>> version >>> `3.8.6` sqlite3-cli/shell now uses only \r\n strings instead of using the >>> default new line in the OS. >>> >>> You mean in CSV output mode, apparently. That's the only time that the >> CLI >> generates \r\n regardless of OS. >> >> >> >> This broke badly a spawned parser of mine but I'd like to know the >>> rationale behind this choice, >>> >>> Because RFC4180 requires it. >> >> > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users