From: Mark M. <mie...@gm...> - 2012-10-23 02:57:25
|
Okay, I worked out the build problems, I think. If you update your source tree from: http://svn.code.sf.net/p/oorexx/code-0/sandbox/mark/ooSQLite.encrypted You should be able to build either 32-bit or 64-bit without problems. I did a cross-compile 32-bit build and put both a 64-bit and 32-bit Windows distribution on SourceForge at: https://sourceforge.net/projects/oorexx/files/ooSQLite/Experimental/ For the lack of a svn info problem: when the build is run, it creates a file: src/ooSQLite.ver.incl If there is no svn info on your system, the first time this file is created it will have in it: OOSQLITE_BLD_LVL=0 OOSQLITE_VER_STR="1.0.0.0" OOSQLITE_COPY_YEAR="2012-2012" SVN_REVSION=0 Once that file is created, you can edit the lines to, for example: OOSQLITE_BLD_LVL=8531 OOSQLITE_VER_STR="1.0.0.8531" OOSQLITE_COPY_YEAR="2012-2012" SVN_REVSION=8531 The build no longer deletes that file when there is no svn info. So you can manually update the file if you want to keep your version string somewhat up-to-date. If you want the version string updated automatically, then you will have to install a svn command line client. Please test the pre-built 32-bit package if you want to. I can not test it until this weekend, but it should be good. These methods / functions have been added to ooSQLite: .ooSQLite~encryptionAvailable (class method of .ooSQLite) ooSQLiteEncryptionAvailable (function) They both take no arguments and return .true when the Botan cryptographic library is linked in, and return .false otherwise. The version method and function for the One-line format return this when the Botan library is linked in: ooSQLite Version 1.0.0.8531 (64 bit) (Encryption enabled) and this for the full format when the library is linked in: ooSQLite: ooSQLite Version 1.0.0.8531 (64 bit) (Encryption enabled) Built Oct 22 2012 19:14:40 Copyright (c) RexxLA 2012-2012. All Rights Reserved. Rexx: Open Object Rexx Version 4.2.0 SQLite: SQLite Library Version 3.7.14.1 2012-10-04 19:37:12 If the library is not linked in, then the (Encryption enabled) substring is simply missing. Let me know if there are any more problems, I don't have time to do much testing of this right now. -- Mark Miesfeld |
From: Staffan T. <sta...@gm...> - 2012-10-23 08:57:05
|
> > > Please test the pre-built 32-bit package if you want to. I can not test > it until this weekend, but it should be good. > > Thanks Mark, I will certainly look into this today and provide my feedback. This morning I had a good/bad idea (delete as you feel fit): Instead of providing botan as an ooSQLite extension (I guess that is what it is), why not provide it as standard in the form of a DLL with ooRexx instead? I can see several benefits doing that, such as future support for encrypted streams, encrypted ftp, encrypted tcpip, in short anything you want. Having the crypto library packaged with ooSQLite reduces its usability. ooRexx would stand out against the rest if it had encryption support already built in, and in today's world this is getting more and more important. And the ooSQLite footprint will be back to what it was before ;) I increase my 2p to 4p worth on this one :) Staffan |
From: Staffan T. <sta...@gm...> - 2012-10-23 10:54:48
|
Mark this is the output from an attempt to build using the recent update you made. I did an svn update prior to this , assuming that the location of the source hasn't changed (the update worked so I guess all is OK). "svn" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable. Copying x86 Botan files 1 archivo(s) copiado(s). 1 archivo(s) copiado(s). cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /Fo.\build\rele ase\ src\sqlite\sqlite3.c sqlite3.c cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /Fo.\build\rele ase\ src\ooSQLite.cpp ooSQLite.cpp cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /Fo.\build\rele ase\ src\APICommon.cpp APICommon.cpp cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /Fo.\build\rele ase\ src\sqlite\codec.cpp codec.cpp cl /nologo /EHs /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /wd4244 /wd4267 /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLI TE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""20 12-2012"\" /I src\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /DNOMINMAX /D:_X86_ /DWIN32 /DNDEBUG / DNULL=0 /c /Fo.\build\release\ src\sqlite\botan_all.cpp botan_all.cpp src\sqlite\botan_all.cpp(3459) : error C2664: 'std::make_pair' : cannot convert parameter 1 from 'const Botan::byte [2]' to 'const unsigned char *&&' You cannot bind an lvalue to an rvalue reference src\sqlite\botan_all.cpp(3476) : error C2664: 'std::make_pair' : cannot convert parameter 1 from 'const Botan::byte [2]' to 'const unsigned char *&&' You cannot bind an lvalue to an rvalue reference NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\cl.EXE"' : return code '0x2' Stop. I guess the "svn" problem at the beginning is caused by the fact that I don't have an SVN batch interface. Staffan |
From: hakan <he...@us...> - 2012-10-23 16:56:56
|
Just a note from me, that I successfully built a FTS version from Mark's sandbox source. Both 32 & 64 bits ( for 32bits I had to remove /Gr from CFLAGS) I use VS 2010 /hex ----- Ursprungligt Meddelande ----- Från: Staffan Tylen <sta...@gm...> Till: Open Object Rexx Users <oor...@li...> Kopia: Datum: tisdag, 23 oktober 2012 12:54 Ämne: Re: [Oorexx-users] ooSQLite with encryption, update Mark this is the output from an attempt to build using the recent update you made. I did an svn update prior to this , assuming that the location of the source hasn't changed (the update worked so I guess all is OK). "svn" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable. Copying x86 Botan files 1 archivo(s) copiado(s). 1 archivo(s) copiado(s). cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /Fo.\build\rele ase\ src\sqlite\sqlite3.c sqlite3.c cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /Fo.\build\rele ase\ src\ooSQLite.cpp ooSQLite.cpp cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /Fo.\build\rele ase\ src\APICommon.cpp APICommon.cpp cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /Fo.\build\rele ase\ src\sqlite\codec.cpp codec.cpp cl /nologo /EHs /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /wd4244 /wd4267 /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLI TE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" /DOOSQLITE_COPYRIGHT_YEAR=\""20 12-2012"\" /I src\sqlite /DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /DNOMINMAX /D:_X86_ /DWIN32 /DNDEBUG / DNULL=0 /c /Fo.\build\release\ src\sqlite\botan_all.cpp botan_all.cpp src\sqlite\botan_all.cpp(3459) : error C2664: 'std::make_pair' : cannot convert parameter 1 from 'const Botan::byte [2]' to 'const unsigned char *&&' You cannot bind an lvalue to an rvalue reference src\sqlite\botan_all.cpp(3476) : error C2664: 'std::make_pair' : cannot convert parameter 1 from 'const Botan::byte [2]' to 'const unsigned char *&&' You cannot bind an lvalue to an rvalue reference NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\cl.EXE"' : return code '0x2' Stop. I guess the "svn" problem at the beginning is caused by the fact that I don't have an SVN batch interface. Staffan ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Oorexx-users mailing list Oor...@li... https://lists.sourceforge.net/lists/listinfo/oorexx-users |
From: Staffan T. <sta...@gm...> - 2012-10-23 17:05:08
|
> ** > Just a note from me, that I successfully built a FTS version from Mark's > sandbox source. > Both 32 & 64 bits ( for 32bits I had to remove /Gr from CFLAGS) > I use VS 2010 > /hex > > IMHO it should be there by default. Anyone? Staffan |
From: hakan <he...@us...> - 2012-10-23 17:46:49
|
I second that, and also support for more tokenizer in the FTS, default today is "simple" "An FTS tokenizer is a set of rules for extracting terms from a document or basic FTS full-text query." Like SQLITE_ENABLE_ICU and /DSQLITE_ENABLE_FTS4_UNICODE61 I think this maybe can solve national character search, problems, with tokenizer "simple" in FTS tables /hex ----- Ursprungligt Meddelande ----- Från: Staffan Tylen <sta...@gm...> Till:<he...@us...> , Open Object Rexx Users <oor...@li...> Kopia: Datum: tisdag, 23 oktober 2012 19:05 Ämne: Re: [Oorexx-users] ooSQLite with encryption, update Just a note from me, that I successfully built a FTS version from Mark's sandbox source. Both 32 & 64 bits ( for 32bits I had to remove /Gr from CFLAGS) I use VS 2010 /hex IMHO it should be there by default. Anyone? Staffan |
From: Staffan T. <sta...@gm...> - 2012-10-23 17:57:55
|
> > Like SQLITE_ENABLE_ICU and /DSQLITE_ENABLE_FTS4_UNICODE61 > I think this maybe can solve national character search, problems, with > tokenizer "simple" in FTS tables > Good point. In short, the fewer restrictions by default, the more useful is the product. Staffan |
From: Mark M. <mie...@gm...> - 2012-10-23 18:08:59
|
On Tue, Oct 23, 2012 at 10:46 AM, hakan <he...@us...>wrote: > ** > I second that, and also support for more tokenizer in the FTS, default > today is "simple" > > "An FTS tokenizer is a set of rules for extracting terms from a document > or basic FTS full-text query." > > Like SQLITE_ENABLE_ICU and /DSQLITE_ENABLE_FTS4_UNICODE61 > I looked at ICU. The build would need to link to that library to be able to do SQLITE_ENABLE_ICU. This looks interesting to me, but more than I'm prepared to do in 2012. Strings coming through Rexx will not be unicode. The ICU library might make it possible to translate the Rexx strings to UNICODE, but of course you would not be able to use the full range of UNICODE characters. There would need to be some method to allow you to put UNICODE strings into the database. Perhaps a way to load the strings from a file that is not filtered through Rexx. Or a method that would allow creating a Rexx buffer object filled with bytes. All, in all it would take considerable work over what is currently available in ooSQLite. -- Mark Miefeld |
From: hakan <he...@us...> - 2012-10-23 18:29:07
|
Mark take you time :-) even if I am old, I can wait ;-). Just wanted to add something to the wish list, to be considered as future development. But enabling FTS (simple) is just simple, so I suggest as Staffan does, make it default enabled. /hex ----- Ursprungligt Meddelande ----- Från: Mark Miesfeld <mie...@gm...> Till:<he...@us...> , Open Object Rexx Users <oor...@li...> Kopia: Datum: tisdag, 23 oktober 2012 20:09 Ämne: Re: [Oorexx-users] ooSQLite with encryption, update On Tue, Oct 23, 2012 at 10:46 AM, hakan <he...@us...> wrote: I second that, and also support for more tokenizer in the FTS, default today is "simple" "An FTS tokenizer is a set of rules for extracting terms from a document or basic FTS full-text query." Like SQLITE_ENABLE_ICU and /DSQLITE_ENABLE_FTS4_UNICODE61 I looked at ICU. The build would need to link to that library to be able to do SQLITE_ENABLE_ICU. This looks interesting to me, but more than I'm prepared to do in 2012. Strings coming through Rexx will not be unicode. The ICU library might make it possible to translate the Rexx strings to UNICODE, but of course you would not be able to use the full range of UNICODE characters. There would need to be some method to allow you to put UNICODE strings into the database. Perhaps a way to load the strings from a file that is not filtered through Rexx. Or a method that would allow creating a Rexx buffer object filled with bytes. All, in all it would take considerable work over what is currently available in ooSQLite. -- Mark Miefeld |
From: Mark M. <mie...@gm...> - 2012-10-23 17:34:11
|
On Tue, Oct 23, 2012 at 10:04 AM, Staffan Tylen <sta...@gm...>wrote: > > ** >> Just a note from me, that I successfully built a FTS version from Mark's >> sandbox source. >> Both 32 & 64 bits ( for 32bits I had to remove /Gr from CFLAGS) >> I use VS 2010 >> /hex >> >> > IMHO it should be there by default. Anyone? Do you mean the FTS extension should be built by default? If so, I kind of agree. If you mean the /Gr flag should be removed by default, I'm not sure about that. It would need some research. -- Mark Miesfeld |
From: Staffan T. <sta...@gm...> - 2012-10-23 17:47:46
|
Do you mean the FTS extension should be built by default? If so, I kind of > agree. > > If you mean the /Gr flag should be removed by default, I'm not sure about > that. It would need some research. > > I meant FTS. Staffan |
From: Rick M. <obj...@gm...> - 2012-10-23 11:04:34
|
On Tue, Oct 23, 2012 at 4:56 AM, Staffan Tylen <sta...@gm...>wrote: > >> Please test the pre-built 32-bit package if you want to. I can not test >> it until this weekend, but it should be good. >> >> > Thanks Mark, I will certainly look into this today and provide my feedback. > > This morning I had a good/bad idea (delete as you feel fit): Instead of > providing botan as an ooSQLite extension (I guess that is what it is), why > not provide it as standard in the form of a DLL with ooRexx instead? I can > see several benefits doing that, such as future support for encrypted > streams, encrypted ftp, encrypted tcpip, in short anything you want. Having > the crypto library packaged with ooSQLite reduces its usability. ooRexx > would stand out against the rest if it had encryption support already built > in, and in today's world this is getting more and more important. And the > ooSQLite footprint will be back to what it was before ;) > I guess I had a bad understanding of what botan was in the context of SQLite. I didn't realize it was a general purporse crypto library. This certainly would be a good general addition to ooRexx, particularly if it meant we could provide SSL support. I do have one concern about whether there are any US export concerns with distributing ooRexx with crypto support. I suspect that the botan people have already dealt with that issue, be we need to check on it. Maybe we really should consider building a separate dll with some suitable API wrappers for ooRexx. Rick > > I increase my 2p to 4p worth on this one :) > > Staffan > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |
From: Staffan T. <sta...@gm...> - 2012-10-23 11:13:27
|
> > > I guess I had a bad understanding of what botan was in the context of > SQLite. I didn't realize it was a general purporse crypto library. This > certainly would be a good general addition to ooRexx, particularly if it > meant we could provide SSL support. I do have one concern about whether > there are any US export concerns with distributing ooRexx with crypto > support. I suspect that the botan people have already dealt with that > issue, be we need to check on it. Maybe we really should consider building > a separate dll with some suitable API wrappers for ooRexx. > > Rick, as botan is open source, can that be restricted by a US export rule? I can't really see how. Staffan |
From: Rick M. <obj...@gm...> - 2012-10-23 11:21:28
|
On Tue, Oct 23, 2012 at 7:12 AM, Staffan Tylen <sta...@gm...>wrote: > >> I guess I had a bad understanding of what botan was in the context of >> SQLite. I didn't realize it was a general purporse crypto library. This >> certainly would be a good general addition to ooRexx, particularly if it >> meant we could provide SSL support. I do have one concern about whether >> there are any US export concerns with distributing ooRexx with crypto >> support. I suspect that the botan people have already dealt with that >> issue, be we need to check on it. Maybe we really should consider building >> a separate dll with some suitable API wrappers for ooRexx. >> >> > Rick, as botan is open source, can that be restricted by a US export rule? > I can't really see how. > Yes it can. I had a bit of experience with this in my last job at IBM, which was working on Apache Geronimo (an open source web server). Just because the source is open doesn't mean it can be classified as an "armament" by the government. The rules for this, unfortunately, are somewhat arbitrary and generally out of date with respect to the current state of the world. The solution was frequently to not ship the crypto libraries directly, but build in support that could use the crypto libraries if they have been downloaded and installed separately. Rick > > Staffan > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |
From: Rick M. <obj...@gm...> - 2012-10-23 12:09:37
|
I sent an email to the botan developer's list. I did find this at the open source initiative: http://opensource.org/node/505 So there is a minimum requirement of notifying the gov that we are distributing cryptography software and letting them know where the source is located. It appears we also have to change the sourceforge product status to indicate we have crypto software and take steps to ensure it is still fully downloadable. Rick On Tue, Oct 23, 2012 at 7:12 AM, Staffan Tylen <sta...@gm...>wrote: > >> I guess I had a bad understanding of what botan was in the context of >> SQLite. I didn't realize it was a general purporse crypto library. This >> certainly would be a good general addition to ooRexx, particularly if it >> meant we could provide SSL support. I do have one concern about whether >> there are any US export concerns with distributing ooRexx with crypto >> support. I suspect that the botan people have already dealt with that >> issue, be we need to check on it. Maybe we really should consider building >> a separate dll with some suitable API wrappers for ooRexx. >> >> > Rick, as botan is open source, can that be restricted by a US export rule? > I can't really see how. > > Staffan > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |
From: Mark M. <mie...@gm...> - 2012-10-23 12:29:00
|
Staffan, Try the per-built distribution: ooSQLite_1_0_0_8531_x86_32win.zip<http://sourceforge.net/projects/oorexx/files/ooSQLite/Experimental/ooSQLite_1_0_0_8531_x86_32win.zip/download> at: https://sourceforge.net/projects/oorexx/files/ooSQLite/Experimental/<https://sourceforge.net/projects/oorexx/files/ooSQLite/Experimental/?> -- Mark Miesfeld On Tue, Oct 23, 2012 at 3:54 AM, Staffan Tylen <sta...@gm...>wrote: > Mark this is the output from an attempt to build using the recent update > you made. I did an svn update prior to this , assuming that the location of > the source hasn't changed (the update worked so I guess all is OK). > > "svn" no se reconoce como un comando interno o externo, > programa o archivo por lotes ejecutable. > Copying x86 Botan files > 1 archivo(s) copiado(s). > 1 archivo(s) copiado(s). > cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 > /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE > /DOOSQLITE_VER_MAJOR=1 > /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 > /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s > rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 > /DNDEBUG /DNULL=0 /c /Fo.\build\rele > ase\ src\sqlite\sqlite3.c > sqlite3.c > cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 > /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE > /DOOSQLITE_VER_MAJOR=1 > /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 > /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s > rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 > /DNDEBUG /DNULL=0 /c /Fo.\build\rele > ase\ src\ooSQLite.cpp > ooSQLite.cpp > cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 > /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE > /DOOSQLITE_VER_MAJOR=1 > /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 > /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s > rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 > /DNDEBUG /DNULL=0 /c /Fo.\build\rele > ase\ src\APICommon.cpp > APICommon.cpp > cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 > /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE > /DOOSQLITE_VER_MAJOR=1 > /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 > /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s > rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 > /DNDEBUG /DNULL=0 /c /Fo.\build\rele > ase\ src\sqlite\codec.cpp > codec.cpp > cl /nologo /EHs /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /wd4244 > /wd4267 /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLI > TE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 > /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""20 > 12-2012"\" /I src\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /DNOMINMAX /D:_X86_ > /DWIN32 /DNDEBUG / > DNULL=0 /c /Fo.\build\release\ src\sqlite\botan_all.cpp > botan_all.cpp > src\sqlite\botan_all.cpp(3459) : error C2664: 'std::make_pair' : cannot > convert parameter 1 from 'const Botan::byte [2]' to 'const unsigned char > *&&' > You cannot bind an lvalue to an rvalue reference > src\sqlite\botan_all.cpp(3476) : error C2664: 'std::make_pair' : cannot > convert parameter 1 from 'const Botan::byte [2]' to 'const unsigned char > *&&' > You cannot bind an lvalue to an rvalue reference > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual > Studio 11.0\VC\BIN\cl.EXE"' : return code '0x2' > Stop. > > I guess the "svn" problem at the beginning is caused by the fact that I > don't have an SVN batch interface. > > Staffan > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |
From: Staffan T. <sta...@gm...> - 2012-10-23 17:36:46
|
> > > Try the per-built distribution: ooSQLite_1_0_0_8531_x86_32win.zip<http://sourceforge.net/projects/oorexx/files/ooSQLite/Experimental/ooSQLite_1_0_0_8531_x86_32win.zip/download> > > at: > > https://sourceforge.net/projects/oorexx/files/ooSQLite/Experimental/<https://sourceforge.net/projects/oorexx/files/ooSQLite/Experimental/?> > > Yup, it seems to be working. Staffan |
From: Staffan T. <sta...@gm...> - 2012-10-26 22:14:00
|
Mark, I just tried compiling ooSQLite again as I found there was an update to the makefile, but only to discover the same problem that I reported before (see below) which we never discussed. However I searched the web and found this: http://connect.microsoft.com/VisualStudio/feedback/details/691756/std-make-pair-error-in-vc11 So it seems like this issue was introduced with VC11 because VC11 corrects an old problem in the earlier compilers. As this affects botan only, will this be reported to them or will you fix this locally? I'm not in a need for a fix personally, it's more a general question how it will/should be handled. Thanks, Staffan Copying x86 Botan files > 1 archivo(s) copiado(s). > 1 archivo(s) copiado(s). > cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 > /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE > /DOOSQLITE_VER_MAJOR=1 > /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 > /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s > rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 > /DNDEBUG /DNULL=0 /c /Fo.\build\rele > ase\ src\sqlite\sqlite3.c > sqlite3.c > cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 > /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE > /DOOSQLITE_VER_MAJOR=1 > /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 > /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s > rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 > /DNDEBUG /DNULL=0 /c /Fo.\build\rele > ase\ src\ooSQLite.cpp > ooSQLite.cpp > cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 > /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE > /DOOSQLITE_VER_MAJOR=1 > /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 > /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s > rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 > /DNDEBUG /DNULL=0 /c /Fo.\build\rele > ase\ src\APICommon.cpp > APICommon.cpp > cl /nologo /EHsc /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /W3 > /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE > /DOOSQLITE_VER_MAJOR=1 > /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=1 > /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""2012-2012"\" /I s > rc\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /D:_X86_ /DWIN32 > /DNDEBUG /DNULL=0 /c /Fo.\build\rele > ase\ src\sqlite\codec.cpp > codec.cpp > cl /nologo /EHs /O2 /Gr /Gs /Gy /FAs /Fabuild\release\ /MT /wd4244 > /wd4267 /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLI > TE_VER_MAJOR=1 /DOOSQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 > /DOOSQLITE_VER_BUILD=1 /DOOSQLITE_VER_STRING="1.0.0.NONE" > /DOOSQLITE_COPYRIGHT_YEAR=\""20 > 12-2012"\" /I src\sqlite /DSQLITE_ENABLE_COLUMN_METADATA > /DSQLITE_ENABLE_MEMORY_MANAGEMENT /DSQLITE_HAS_CODEC=1 /DNOMINMAX /D:_X86_ > /DWIN32 /DNDEBUG / > DNULL=0 /c /Fo.\build\release\ src\sqlite\botan_all.cpp > botan_all.cpp > src\sqlite\botan_all.cpp(3459) : error C2664: 'std::make_pair' : cannot > convert parameter 1 from 'const Botan::byte [2]' to 'const unsigned char > *&&' > You cannot bind an lvalue to an rvalue reference > src\sqlite\botan_all.cpp(3476) : error C2664: 'std::make_pair' : cannot > convert parameter 1 from 'const Botan::byte [2]' to 'const unsigned char > *&&' > You cannot bind an lvalue to an rvalue reference > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual > Studio 11.0\VC\BIN\cl.EXE"' : return code '0x2' > Stop. > > |
From: Mark M. <mie...@gm...> - 2012-10-27 05:49:29
|
On Fri, Oct 26, 2012 at 3:13 PM, Staffan Tylen <sta...@gm...>wrote: > Mark, I just tried compiling ooSQLite again as I found there was an update > to the makefile, but only to discover the same problem that I reported > before (see below) which we never discussed. However I searched the web and > found this: > > > http://connect.microsoft.com/VisualStudio/feedback/details/691756/std-make-pair-error-in-vc11 > > So it seems like this issue was introduced with VC11 because VC11 corrects > an old problem in the earlier compilers. As this affects botan only, will > this be reported to them or will you fix this locally? Probably neither. The Botan people are aware of this I'm sure. The 1.10 version I snatched is guaranteed to compile with VC++ 10. The next version, 1.11 requires a C++ 11 compliant compiler. Including encryption in ooSQLite is stalled at this point. We have discussed this on the developers list. Making encryption software available is tightly regulated and controlled by *Export Administration Regulations. While my research leads me to believe that the recent changes in government policy make it ok if the source code is publically available, one of the other developers feels we would still need to register with the EAR and that it is too hard to do.* Until we resolve this among the developers, ooSQLite won't be including encryption. I was hoping to get a reply back from the U. S. Bureau of Industry and Security whom I asked for clarification. But, I haven't received an answer yet. -- Mark Miesfeld |
From: Staffan T. <sta...@gm...> - 2012-10-27 09:35:43
|
> > > Until we resolve this among the developers, ooSQLite won't be including > encryption. > > In a way I think that shipping encryption (botan) as part of ooSQLite is not really necessary, is it? Is there a reason why an end user can not download and install botan separately to ooSQLite? I believe that a large majority of ooRexx users don't have a need for encryption anyway. If ooSQLite (and ooRexx?) have the necessary API to use the botan library, that should be enough as far as I can tell. Having encryption included may create similar problems for those of us who create applications that ship with ooRexx/ooSQLite included in the package, unless the encryption dll is optional. But there is probably something that I haven't thought about here... :( Staffan |