System.Data.SQLite
Check-in [2e77593c0d]
Not logged in

 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ... 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 ... 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 ... 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274   if {[isEagle]} then { ########################################################################### ############################ BEGIN Eagle ONLY ############################# ########################################################################### proc getBuildYear {} { # # NOTE: See if the "year" setting has been overridden by the user (e.g. on # the command line). This helps control exactly which set of # binaries we are testing, those produced using the Visual Studio # 2005, 2008, 2010, or 2012 build systems. To override this value # via the command line, enter a command similar to one of the # following (all on one line): # # EagleShell.exe -preInitialize "set test_year 2005" # -file .\path\to\all.eagle ................................................................................ # return $::eagle_platform(configuration) } } proc getBuildDirectory {} { # # NOTE: See if the "native" runtime option has been added. If so, use the # directory for the mixed-mode assembly (a.k.a. the native interop # assembly). To enable this option via the command line, enter a # command similar to one of the following (all on one line): # # EagleShell.exe -initialize -runtimeOption native # -file .\path\to\all.eagle # ................................................................................ # path. The EagleTest package guarantees that this variable # will be set to the directory containing the first file to # execute the [runTestPrologue] script library procedure. # set path [file dirname$::path] } if {[hasRuntimeOption native]} then { return [file join $path bin [getBuildYear] \ [machineToPlatform$::tcl_platform(machine)] \ [getBuildConfiguration]] } else { return [file join $path bin [getBuildYear] \ [getBuildConfiguration] bin] } } } proc getBuildFileName { fileName } { # # NOTE: Returns the specified file name as if it were located in the ................................................................................ # entire script being returned will be substituted via [subst], in # the context of the caller. This step is necessary so that some # limited context information, primarily related to the test build # directory, can be transferred to the interpreter in the isolated # application domain, making it able to successfully run tests that # require one or more of the files in the build directory. Callers # to this procedure should keep in mind that the test script being # returned cannot only rely on any script library procedures not # included in the Eagle.Library package (i.e. "init.eagle"). Also, # all variable references and all "nested" commands (i.e. those in # square brackets), unless they are specially quoted, will end up # being evaluated in the context of the calling interpreter and not # the test interpreter created in the isolated application domain. # return [uplevel 1 [list subst [appendArgs$prefix { if {[hasRuntimeOption native]} then { object invoke Interpreter.GetActive AddRuntimeOption native   | | | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | < | | < > | | |  16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ... 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 ... 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 ... 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313   if {[isEagle]} then { ########################################################################### ############################ BEGIN Eagle ONLY ############################# ########################################################################### proc getBuildYear {} { # # NOTE: See if the "year" setting has been overridden by the user (e.g. # on the command line). This helps control exactly which set of # binaries we are testing, those produced using the Visual Studio # 2005, 2008, 2010, or 2012 build systems. To override this value # via the command line, enter a command similar to one of the # following (all on one line): # # EagleShell.exe -preInitialize "set test_year 2005" # -file .\path\to\all.eagle ................................................................................ # return $::eagle_platform(configuration) } } proc getBuildDirectory {} { # # NOTE: See if the "native" runtime option has been set. If so, use the # directory for the mixed-mode assembly (a.k.a. the native interop # assembly). To enable this option via the command line, enter a # command similar to one of the following (all on one line): # # EagleShell.exe -initialize -runtimeOption native # -file .\path\to\all.eagle # ................................................................................ # path. The EagleTest package guarantees that this variable # will be set to the directory containing the first file to # execute the [runTestPrologue] script library procedure. # set path [file dirname$::path] } # # NOTE: If the "native" runtime option is set, the mixed-mode assembly # is being tested. In that case, the path to the build directory # will contain the platform name and all the binaries under test # should be present in that directory. If the "native" runtime # option is not set, the build directory will be considered to be # "platform-neutral", with the notable exception of any native # assembly (e.g. "SQLite.Interop.dll") copied there during the # build process itself. If the build process somehow does not # copy the native assembly for this platform, most of the tests # in the suite will simply be skipped. Generally speaking, there # are two ways to build the binaries when preparing to run the # test suite: # # 1. Build the separate managed and native assemblies using some # commands similar to: # # build.bat ${Configuration}ManagedOnly${Platform} # build.bat ${Configuration}NativeOnly${Platform} # # Where ${Configuration} is either "Debug" or "Release" and #${Platform} is either "Win32" or "x64". # # 2. Build the mixed-mode assembly using a command similar to: # # build.bat ${Configuration}${Platform} # # Where ${Configuration} is either "Debug" or "Release" and #${Platform} is either "Win32" or "x64". If this command is # used, various tests that require supplementary managed # assemblies (e.g. LINQ) may be skipped unless those binaries # are subsequently copied into the correct directory (i.e. by # "test_all.bat"). # # Note that all of the build commands above will default to using # the latest version of MSBuild available and the "test_year" may # need to be adjusted accordingly to actually run the test suite. # Refer to the comments in [getBuildYear] for more information on # how to set this variable. # if {[hasRuntimeOption native]} then { return [file join $path bin [getBuildYear] [machineToPlatform \$::tcl_platform(machine)] [getBuildConfiguration]] } else { return [file join $path bin [getBuildYear] [getBuildConfiguration] \ bin] } } } proc getBuildFileName { fileName } { # # NOTE: Returns the specified file name as if it were located in the ................................................................................ # entire script being returned will be substituted via [subst], in # the context of the caller. This step is necessary so that some # limited context information, primarily related to the test build # directory, can be transferred to the interpreter in the isolated # application domain, making it able to successfully run tests that # require one or more of the files in the build directory. Callers # to this procedure should keep in mind that the test script being # returned cannot rely on any script library procedures not defined # by the Eagle.Library package (i.e. "init.eagle"). Also, all # variable references and all "nested" commands (i.e. those in # square brackets), unless they are specially quoted, will end up # being evaluated in the context of the calling interpreter and not # the test interpreter created in the isolated application domain. # return [uplevel 1 [list subst [appendArgs$prefix { if {[hasRuntimeOption native]} then { object invoke Interpreter.GetActive AddRuntimeOption native