Add a builder file to more easily test STL examples with Calypso. Add so... #6
Conversation
… some STL test files also.
|
Yay more STL tests, thanks Kelly! Only why did you put each of them in a separate folder? To avoid them sharing the same calypso_cache files? I don't think that's useful since sharing the same PCH just works (never had a problem with adding more headers) and it doesn't matter if the PCH gets big because it's loaded lazily. I'd prefer the .d files to be all in the same directory. Eventually Calypso will check if the PCH is still valid (i.e if no header files changed in the meantime) so later even deleting the calypso_cache files will be unnecessary. Could you also rename the BUILD file build_stl.sh? Finally please use modmap "<>" whenever possible to avoid collisions with executables, some are missing. |
|
Not sure why I'm always asking you to make the changes, sorry :) . I'll merge this later today and do the changes myself. |
|
Hello Elie, I put each test in a different folder because I was getting some strange and annoying errors when keeping them in the same dir. If you try to build queue.d without removing the previous executable you may see a thousand lines of junk fly up the screen (Linux 3.13). This was happening with a few different files when I started working on Calypso weeks ago, so I put each stl test in its own directory…I thought Calypso might be getting confused with certain remnant .o/exe/pch files. I also wanted to see which cpp elements were being generated by Calypso and an easy way to do that was just to look at the cpp_std...o files that were left in the directory after compiling. I am also allergic to polluting a testing base directory with dozens of executables (after all tests are built). Also, directories like algorithm will probably have a bunch of different files in it at some point to test each algorithm. I would also think separate directories would be preferred later on for testing large libs like OGRE, etc. There could be dozens of test files for a library that size…then multiply that by 15 libs and we have 200 files in the base directory. They need unique naming…tab completion is a pain, etc., etc. Just personal preference on my part for all of this, though, so do whatever you like with it…I won’t be offended :) Sorry, I thought I caught almost all the modmap”<>” changes. Thanks, Kelly From: Elie Morisse [mailto:[email protected]] Yay more STL tests, thanks Kelly! Only why did you put each of them in a separate folder? To avoid them sharing the same calypso_cache files? I don't think that's useful since sharing the same PCH just works (never had a problem with adding more headers) and it doesn't matter if the PCH gets big because it's loaded lazily. I'd prefer the .d files to be all in the same directory. Eventually Calypso will check if the PCH is still valid (i.e if no header files changed in the meantime) so later even deleting the calypso_cache files will be unnecessary. Could you also rename the BUILD file build_stl.sh? Finally please use modmap "<>" whenever possible to avoid collisions with executables, some are missing. — |
Add more C++ standard lib tests and a build script.
...me STL test files also.
Use "./BUILD " for a single file in the named subdirectory test or "./BUILD --all" to test all subdirectories. The D file name to test must be the same as the subdirectory name (ie. bitset/bitset.d).