Jon,
you'll need Rony's statement that it is his work and he contributes it to open
source, to be precise. I'd suggest we have these statements on file, so e.g.
somewhere in version management, but in a directory somewhere out of sight so
we are not bothered too much with it.
best regards,
That sounds like a good idea...I'll create a directory later this morning.
Rick
On Thu, Jun 12, 2014 at 7:30 AM, René Jansen rvjan...@xs4all.nl wrote:
Jon,
you'll need Rony's statement that it is his work and he contributes it to
open source, to be precise. I'd suggest we have these
I always wondered who created classes on the fly
I'm creating methods on the fly. In an optimizer that gets as input a list
of variables with their respective domains (value ranges), and a list of
constraints (something like A+B3 or IsIntegerInRange(A-B*2,0,99) ) I
need to estimate the
Wow,
Now I know and I'm impressed.
Jon
On 12 June 2014 12:59, Erich Steinböck erich.steinbo...@gmail.com wrote:
I always wondered who created classes on the fly
I'm creating methods on the fly. In an optimizer that gets as input a
list of variables with their respective domains (value
Ok, I've created a directory in svn called iclas (Individual Contributor
License Agreements). I create an icla agreement based on the language in
the Apache agreement and a readme file detailing how recording the
agreement should be handled.
Rick
On Thu, Jun 12, 2014 at 7:30 AM, René Jansen
I'm guessing there might need to be some adjustments made in the build
suite for locating information in out-of-source builds. For example, I'm
sure the process of locating the headers required for building the native
api tests will require adjustment. The readme doesn't give any hints about
To locate the header files, the test suite uses the REXX_HOME variable, if
I remember correctly. It also tries to locate the buildDir. So, you could
set REXX_HOME to point to where the header, lib files are.
I've got to go right now, the code is in ::routine locateAPIDir in
building.frm. I'll
Thanks Rick,
I will get to this (but maybe not till next week)
Jon
On 12 June 2014 14:15, Rick McGuire object.r...@gmail.com wrote:
Ok, I've created a directory in svn called iclas (Individual Contributor
License Agreements). I create an icla agreement based on the language in
the Apache
I was taking a look a the test suit to fix this up if needed. Looking at
the code, it seems setting REXX_API to point to:
build\_CPack_Packages\win64\NSIS\ooRexx-4.3.0-win64\DevLib\api
should work.
But, I discovered that rxregexp.dll is not getting built correctly. so the
test suite won't run.
Ok, I think rxregexp should be fixed now. There was a typo in the target
dependencies that prevented it using the .rc and .def file on the link.
The .def file was the kiss of death that prevented it from loading.
Rick
On Thu, Jun 12, 2014 at 3:01 PM, Mark Miesfeld miesf...@gmail.com wrote:
Okay, thanks Rick.
--
Mark Miesfeld
On Thu, Jun 12, 2014 at 12:11 PM, Rick McGuire object.r...@gmail.com
wrote:
Ok, I think rxregexp should be fixed now. There was a typo in the target
dependencies that prevented it using the .rc and .def file on the link.
The .def file was the kiss of
I've gotten confused on the status of packaging on Windows.
To create the NSIS package are we using CPack, going to use CPack but it
isn't ready yet, or ... ?
Thanks.
--
Mark Miesfeld
--
HPCC Systems Open Source Big
I think it is ready to go, although it probably needs a round or two of
testing to make sure everything works. Right now, can build either of two
ways, the non-template based version you did (although this version is
probably out of date with respect to the samples) and the template-based
build I
On Thu, Jun 12, 2014 at 12:47 PM, Rick McGuire object.r...@gmail.com
wrote:
I think it is ready to go, although it probably needs a round or two of
testing to make sure everything works. Right now, can build either of two
ways, the non-template based version you did (although this version is
No, I basically implemented my own version of CPack, leveraging some of the
files produced by the install commands. CMake actually generates a script
that takes care of the hardest parts of the process, so it turned out to be
pretty easy to implement.
I'm finding this version to be incredibly
I also want to say that I find the CMake system to be very flexible and,
after a little education, easy to work with. And highly system
independent.
When I recommended CMake I had no idea it would work as well as it has
for us.
David Ashley
On Thu, 2014-06-12 at 16:16 -0400, Rick McGuire wrote:
Ditto! I really like having just one thing to update when I make a
change...at least once we can get rid of the Makefile.am version. Which
reminds me, I'll need to update that for the changes to the samples...sigh.
It is really beautiful in handling differences between different build
types.
David,
Could you take a look at what needs to be done in Makefile.am for the
changes to the samples? If I read what it's doing correctly, it is just
copying all of the .rex files. However, there are now a couple other files
in that directory (a .cls and a .txt) that would also need to be
Rick -
Looks like you made some spelling errors in either the cmake file or the
file names for
syncronizedConcurrency.rex
usetree.rex
David Ashley
--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk
Rick -
I have to be perfectly honest here. I do not see these updates as
necessary to the old build. As long as the code is up-to-date, I am not
fired up to make the to builds match entirely. Especially since the old
builds will be targeted mostly toward older distributions that will be
going out
20 matches
Mail list logo
