-
Your attached makefiles seem largely ok. The only thing that I noticed is that in makefile.nsk you set OS_SHARED_LIB_PREFIX to the empty string. Yet, in makefile.cpp in the definition of CC_SHAREDLIBNAMEFLAGS you have the prefix set to "lib". They should be the same.
I'm still a bit at a loss as to why you would need to specify -llibSTAF.so instead of just -lSTAF, as the compiler/linker...
2009-11-04 19:27:37 UTC in SW Test Automation Framework
-
Could you post the contents of your build/makefile.nsk and build/makefile.cpp.
2009-11-02 20:44:53 UTC in SW Test Automation Framework
-
Note, unless you are doing very specific things when building on unix, you don't want to put the prefix or suffix. It is the compilers/linkers responsibility to figure out the appropriate prefixes/suffixes.
2009-11-02 19:33:27 UTC in SW Test Automation Framework
-
Are you saying that within one of your STAX jobs, you need to spawn off a system thread instead of a STAX Thread? The embedded Jython in STAX allows you to access anything from Java. Thus, you can use a <script> element to constract a native Java Thread to do whatever you want. Having said that, whenever a STAX Thread is actively running, it is running on a real thread (but not...
2009-03-12 12:45:59 UTC in SW Test Automation Framework
-
I think that somewhere in the feature list is a feature to not have handles restart at 1 when STAFProc restarts. Obviously, we haven't gotten to that one yet. :) Even still, that won't technically solve your problem as handle numbers would ultimately exceed the size of an unsigned int on the platform and rollover, generating the same problem (albeit with much much less frequency).
The STAX...
2008-06-11 14:08:17 UTC in SW Test Automation Framework
-
This is certainly doable. There's been another idea running around for a while, but I'm not sure if we have a feature opened for it (although it is dependent on Featuer #626605: Rewrite Event Service in C++).
Basically, we would have services generate events when various requests were made (and likely when various other situations occur in STAFProc). So, for the LOG service, we would...
2008-06-03 14:27:17 UTC in SW Test Automation Framework
-
I think it has to do with your current directory not being a full "windows definable" path. Try changing your directory to be something like /cygdrive/c//Administrator/build/src/staf.
2008-05-16 15:49:12 UTC in SW Test Automation Framework
-
Would this be purely decorative? Or, are you also expecting the STAX runtime to detect invalid/incorrect throws as well as validating that calling functions contain appropriate s. I.e., do you want it to behave like Java?.
2007-09-05 23:24:59 UTC in SW Test Automation Framework
-
This is an interesting area to me. As you already know, STAF doesn't currently support changing its own environment variables. However, STAF could certainly be changed to allow this. The interesting question is whether it should be?
Bryan, I can definitely see where you are coming from. You don't really share the machine with anyone and you want to make an update that will (positively...
2007-08-02 15:36:42 UTC in SW Test Automation Framework
-
Thanks for the compliments. I'm glad you like STAF/STAX. Note, STAX is most commonly run on a central system where the jobs execute processes remotely. This allows the target system(s) to only run the basic STAF daemon while the "heavyweight" stuff runs on a central system. Would this type of setup work in your situation, or do you actually need STAX (or something similar) to actually run on...
2007-05-14 13:47:34 UTC in SW Test Automation Framework
