You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Adrian Dick (JIRA)" <ax...@ws.apache.org> on 2006/01/23 10:57:10 UTC
[jira] Closed: (AXISCPP-855) Incorrect combinations of
multithreading flags for MS VC++ in ANT scripts
[ http://issues.apache.org/jira/browse/AXISCPP-855?page=all ]
Adrian Dick closed AXISCPP-855:
-------------------------------
Resolution: Invalid
As Henrick suggests, it is not wrong for the test clients to be using the /MD flag (which sets the version of runtime library to be used)
In fact, the advice within the MS VC++ help is that all the DLLs (and EXE) running within a single process should all be using the same runtime libraries to avoid stack issues. Therefore, as the axis runtime libraries are compiled with /MD it is correct that the tests also be compiled with /MD.
> Incorrect combinations of multithreading flags for MS VC++ in ANT scripts
> -------------------------------------------------------------------------
>
> Key: AXISCPP-855
> URL: http://issues.apache.org/jira/browse/AXISCPP-855
> Project: Axis-C++
> Type: Bug
> Components: Build - ANT
> Versions: current (nightly)
> Environment: MS Windows, MS Visual C++
> Reporter: Adrian Dick
> Priority: Minor
>
> I have noticed we're not always using the correct compiler flag when producing multithreaded binaries on Windows with Visual C++.
> Currently, the ANT scripts always use /MD for all built artefacts, but this isn't always correct.
> In production builds (non-debug), the following should be used:
> /MD for all libraries (DLLs) <--- This is currently correct!
> /MT for all executables (EXEs, ie: SimpleAxisServer and test clients)
> In debug builds:
> /MDd for all libraries (DLLs)
> /MTd for all executables (EXEs, ie: SimpleAxisServer and test clients)
> So far, this isn't seen as causing problems on any our testcases, but this could be down to luck, or perhaps our testcases don't stress the system sufficiently to expose the problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira