On Sep 3, 2010, at 6:30 PM, Michael Hertling wrote:
On 09/03/2010 04:13 PM, Belcourt, Kenneth wrote:
On Sep 3, 2010, at 5:07 AM, Eric Noulard wrote:
Curious to know, Why do you want to "some files" files to always be
built debug
in the first place?
For example, certain Lapack routines lik
On 09/03/2010 04:13 PM, Belcourt, Kenneth wrote:
>
> On Sep 3, 2010, at 5:07 AM, Eric Noulard wrote:
>
>> 2010/9/3 Belcourt, Kenneth :
>>> Apologies if this has been answered before. In an effort to ensure
>>> cross-platform consistent results, I need to force some (C++ and
>>> Fortran)
>>> so
On Sep 3, 2010, at 7:51 AM, Michael Hertling wrote:
On 09/03/2010 01:07 PM, Eric Noulard wrote:
2010/9/3 Belcourt, Kenneth :
Hi,
Apologies if this has been answered before. In an effort to ensure
cross-platform consistent results, I need to force some (C++ and
Fortran)
source files to alw
On Sep 3, 2010, at 5:07 AM, Eric Noulard wrote:
2010/9/3 Belcourt, Kenneth :
Apologies if this has been answered before. In an effort to ensure
cross-platform consistent results, I need to force some (C++ and
Fortran)
source files to always be built debug. Is there any easy syntax to
do
On 09/03/2010 01:07 PM, Eric Noulard wrote:
> 2010/9/3 Belcourt, Kenneth :
>> Hi,
>>
>> Apologies if this has been answered before. In an effort to ensure
>> cross-platform consistent results, I need to force some (C++ and Fortran)
>> source files to always be built debug. Is there any easy synta
2010/9/3 Belcourt, Kenneth :
> Hi,
>
> Apologies if this has been answered before. In an effort to ensure
> cross-platform consistent results, I need to force some (C++ and Fortran)
> source files to always be built debug. Is there any easy syntax to do this?
>
> I build our libraries like this.
Hi,
Apologies if this has been answered before. In an effort to ensure
cross-platform consistent results, I need to force some (C++ and
Fortran) source files to always be built debug. Is there any easy
syntax to do this?
I build our libraries like this.
SET(SRCS
${EXEC_DIR}/AfterStep
