WavePacket (C++/Python) / Tickets / #73 Build system cleanups

Ulf Lorenz - 2017-01-02

Milestone: Backlog --> 0.1.3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -1,5 +1,6 @@
-Some issues that were not attacked during ticket [#66]. Basically, make use of CMake's advanced capabilities and features.
+Some issues that were not attacked during ticket [#66]. Basically, make use of CMake's advanced capabilities and features and fix bugs or so:

+* fix: Wavepacket is always built as shared library.
 * improve test handling
     * add custom target for running the unit tests (CTest target?)
     * add custom targets for building and running individual tests, if still needed

Tickets: ~~#66~~

Ulf Lorenz - 2017-03-15

Milestone: 0.1.3 --> 0.1.4
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -1,13 +1,13 @@
 Some issues that were not attacked during ticket [#66]. Basically, make use of CMake's advanced capabilities and features and fix bugs or so:

-* fix: Wavepacket is always built as shared library.
-* improve test handling
-    * add custom target for running the unit tests (CTest target?)
-    * add custom targets for building and running individual tests, if still needed
+* fix: Wavepacket is always built as shared library by default
 * enable automatic installation of tensor library and its required libs
-* get a Windows build up and running
 * version the installations so that multiple versions / builds can coexist on the same system
 * add a header file with various build settings (e.g., version). Needed anywhere?
 * use/add demos as regression tests
-    * add all demos as CTest test cases
+    * add all demos as CTest test cases and allow somehow to run them regularily
     * compare demo output against fixed reference output 
+
+Optional further issues:
+
+* get a Windows build up and running

Tickets: ~~#66~~

Ulf Lorenz - 2017-03-23

Description has changed:

Diff:

--- old +++ new @@ -11,3 +11,4 @@ Optional further issues: * get a Windows build up and running +* Is it possible to work around CMake warnings if the boost library is much more recent than the cmake version?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ulf Lorenz - 2017-04-23

Milestone: 0.1.4 --> Backlog
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -6,7 +6,9 @@
 * add a header file with various build settings (e.g., version). Needed anywhere?
 * use/add demos as regression tests
     * add all demos as CTest test cases and allow somehow to run them regularily
-    * compare demo output against fixed reference output 
+    * compare demo output against fixed reference output
+* better usage for end users: have a script or so that compiles a handful of files with default settings.
+    * WavePacket could be built with debug and release version, and a flag changes between the two.

 Optional further issues:

summary: Finalize build system upgrade --> Build system cleanups
Description has changed:

Diff:

--- old
+++ new
@@ -1,16 +1,8 @@
 Some issues that were not attacked during ticket [#66]. Basically, make use of CMake's advanced capabilities and features and fix bugs or so:

 * fix: Wavepacket is always built as shared library by default
-* enable automatic installation of tensor library and its required libs
+* better usage for end users: have a script or Makefile that compiles a handful of files with default settings.
 * version the installations so that multiple versions / builds can coexist on the same system
 * add a header file with various build settings (e.g., version). Needed anywhere?
-* use/add demos as regression tests
-    * add all demos as CTest test cases and allow somehow to run them regularily
-    * compare demo output against fixed reference output
-* better usage for end users: have a script or so that compiles a handful of files with default settings.
-    * WavePacket could be built with debug and release version, and a flag changes between the two.
-
-Optional further issues:
-
-* get a Windows build up and running
+    * WavePacket could be built with debug _and_ release version, and a flag changes between the two.
 * Is it possible to work around CMake warnings if the boost library is much more recent than the cmake version?

Tickets: ~~#66~~

Ulf Lorenz - 2017-11-11

Milestone: Backlog --> 0.3 goal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ulf Lorenz - 2017-12-03

Milestone: 0.3 goal --> 0.2.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ulf Lorenz - 2017-12-15

status: open --> assigned

assigned_to: Ulf Lorenz
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -6,3 +6,7 @@
 * add a header file with various build settings (e.g., version). Needed anywhere?
     * WavePacket could be built with debug _and_ release version, and a flag changes between the two.
 * Is it possible to work around CMake warnings if the boost library is much more recent than the cmake version?
+
+----
+
+Many issues defered to ticket [#118]. Essentially, I only documented the shared library stuff and added a script to simplify the compilation. For reasons, see the followup ticket.

status: assigned --> done
assigned_to: Ulf Lorenz --> nobody

Tickets: #118

Build system cleanups

Time-dependent simulation of open and closed quantum systems

Milestone

Searches

Help

#73 Build system cleanups

Related

Discussion

Related

Related

Related

Related