Reply to thread

Message

compile time

Compile time will be dependent on how powerful your hardware is. What kind of machine are you running? It's been a few days since you posted your question. How are things working out?

Also, if I remember correctly, the default compilation process included running the test suite after the creation of the libraries & executables. The test suite execution takes *much* longer if you build in debug mode. This is why I suggested changing the active solution in the most recent set of instructions:

Change the active solution from "Debug CRTDLL" to "Release CRTDLL" by selecting "Build/Configuration Manager" in VS2008

If it is the build process itself that is taking the time, then 14 hours is plausible if you are running a slower machine. It's been a couple of months since I built quantlib but I remember it taking a couple of hours to build the executables and then about an hour to run the test cases on a medium speed core2 duo box. Prior to that I was running a 2.8 ghz / 1 gb pentium 4 and it took 4 or 5 hours to do the build. All this is from memory so don't be too surprised if your results vary.

Also, I was using Visual Studio 2008, express edition ( the free version). This may not be necessary but if possible, you might want to consider switching just to eliminate a source of variation of results.

Hope this helps.

Happy New Year!

- Dave

<blockquote data-quote="DaveCompton" data-source="post: 12343" data-attributes="member: 712">compile timeCompile time will be dependent on how powerful your hardware is.&nbsp; What kind of machine are you running?&nbsp; &nbsp; It&#039;s been a few days since you posted your question.&nbsp; How are things working out?Also,&nbsp; if I remember correctly, the default compilation process included running the test suite after the creation of the libraries &amp; executables.&nbsp; The test suite execution takes *much* longer if you build in debug mode.&nbsp; This is why I suggested changing the active solution in the most recent set of instructions:&nbsp; Change the active solution from &quot;Debug CRTDLL&quot; to &quot;Release CRTDLL&quot; by selecting &quot;Build/Configuration Manager&quot; in VS2008If it is the build process itself that is taking the time, then 14 hours is plausible if you are running a slower machine.&nbsp; &nbsp; It&#039;s been a couple of months since I built quantlib but I remember it taking a couple of hours to build the executables and then about an hour to run the test cases on a medium speed core2 duo box.&nbsp; Prior to that I was running a 2.8 ghz / 1 gb pentium 4 and it took 4 or 5 hours to do the build.&nbsp; All this is from memory so don&#039;t be too surprised if your results vary.Also, I was using Visual Studio 2008, express edition ( the free version).&nbsp; This may not be necessary but if possible, you might want to consider switching just to eliminate a source of variation of results.Hope this helps.Happy New Year!- Dave</blockquote>

[QUOTE="DaveCompton, post: 12343, member: 712"] [b]compile time[/b] Compile time will be dependent on how powerful your hardware is. What kind of machine are you running? It's been a few days since you posted your question. How are things working out? Also, if I remember correctly, the default compilation process included running the test suite after the creation of the libraries & executables. The test suite execution takes *much* longer if you build in debug mode. This is why I suggested changing the active solution in the most recent set of instructions: [B]Change the active solution from "Debug CRTDLL" to "Release CRTDLL" by selecting "Build/Configuration Manager" in VS2008 [/B] If it is the build process itself that is taking the time, then 14 hours is plausible if you are running a slower machine. It's been a couple of months since I built quantlib but I remember it taking a couple of hours to build the executables and then about an hour to run the test cases on a medium speed core2 duo box. Prior to that I was running a 2.8 ghz / 1 gb pentium 4 and it took 4 or 5 hours to do the build. All this is from memory so don't be too surprised if your results vary. Also, I was using Visual Studio 2008, express edition ( the free version). This may not be necessary but if possible, you might want to consider switching just to eliminate a source of variation of results. Hope this helps. Happy New Year! - Dave [/QUOTE]

Verification