-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.1.0 #18
base: master
Are you sure you want to change the base?
1.1.0 #18
Conversation
Remove several warnings printed when running swig by renaming the relevant functions to ones that are compatible with Java. Started working on porting the VTO interfaces to be Swig compatible. (Swig prefers "static const" over "const static.")
Linux and Windows handle case sensitivity differently. Namely, the former thinks that "dnp3test" and "DNP3Test" are different, while the latter believes that they are (mistakenly) the same. Since we generate binaries that match directories in a case insensitive manner (dnp3test->DNP3Test and testset->TestSet), simply adding 'dnp3test' and 'testset' to the .gitignore causes the source code directories with the "same" name to also be ignored. This isn't what we want, so the trick is to tell git to ignore the binaries but include the directories. We do this using the "negate" operator and the "directory-slash" suffix. These rules are at the top of the .gitignore so that all the other rules (like ignoring object files, swap files, etc.) behave like one would expect.
Thanks to William Sember for catching the non-thread-safe code generated by Swig. http://matt.eifelle.com/2007/11/23/enabling-thread-support-in-swig-and-python/
Conflicts: .gitignore
Support for 'make -j X' (where X is the number of parallel build threads to execute) now works properly for the Java Swig bindings.
Link local connections do not work. You need to bind to a global or loopback address.
Helps with backwards compatibility of existing testset XML files
Conflicts: DNP3/StartupTasks.cpp
Moved the ConvertMode() function to being owned by the XmlToConfig class
Moved the ConvertMode() function to being owned by the XmlToConfig class
For a master stack in testset, enabling time sync support was hardcoded to 'true'. This prevented testing with testset where time sync needs to be disabled on the master stack. Now we read the property and feed it into the master stack configuration struct properly.
This apparently includes contributions from William Sember, do you know him? We don't have a CLA for him at the moment, which is problematic. |
No, I don't know glaslos personally. He submitted these to my fork for inclusion. The patches looked good, just like I would have done, so I pulled it in rather than retyping the fix that he made. |
I was thinking about the "Added Python Master demo from William Sember" commit. I just need to figure out legal issues with these contributions. |
Oh, but do you really care, since the commit is coming through me, and I have a CLA signed? |
Guys has this been resolved? |
Created release 1.1.0, which includes a variety of bug fixes since 1.0.0.