Jc - 6/8/2011:

Internally, CMake relies on KWSys which handle dates (see here line 705). But the date/time methods are not exposed at the scripting level.

Not sure to understand the problem you described. The date is supposed to be numerical. Isn't it ? Is there special character displayed?

If you issue the command "cmd /c "date /T" in a windows terminal, could you send a screenshot of the result ?

If we don't find a obvious way to resolve that issue, I see the following option:
1) Relying on python to obtain the date [Don't like that since python is a build option]

2) "Try_compile" a small executable allowing to obtain the date

Thanks
Jc

Steve - 6/8/2011:

Hi Jc -

We couldn't find a print-screen key on the laptop so I took a phone
photo and sent it to you.

The output comes up with the Chinese characters for "Thursday" after
the numeric date (the machine is set to Chinese time, so it's Thursday
already ;) In the English version the string is "Wed 2011-06-08".

I agree on the two options you mentioned. I don't see any easier
workaround that will be robust. For slicer purposes at this point I
think python could be considered a requirement, at least for the
purposes of making dated packages, so that is probably the easier
solution. Longer term I would suggest exposing the KWSys calls in
cmake as the more useful solution.

For now though we hacked around this issue on Luping's machine so it's
not a high priority fix. We'll see what other issues occur, but so
far Luping's build has been going for several hours so this may be the
only issue we see.

Considering the function "SlicerFunctionToday" isn't used anymore. Will consider this issue is resolved.

See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=20028