Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. ATL MFC troubles

ATL MFC troubles

Scheduled Pinned Locked Moved C / C++ / MFC
c++csharpvisual-studiocomtools
4 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    Bob Stanneveld
    wrote on last edited by
    #1

    Hello, I'm developing an application using Visual Studio 2005. I use MFC and eveything was working (the prototypes, the application layer, eveything) until I set up the integration project. Everything compiled with a lot of warnings. I fixed them (mostly deprecated warnings that I suppress using the _CRT_SECURE_NO_DEPRECATE define). After fixing the warnings, errors stared to appead from every GUI file it was compiling. The 5 errors that keep coming back are:

    c:\program files\microsoft visual studio 8\vc\atlmfc\include\atltime.h(393) : error C3861: '_localtime64_s': identifier not found
    c:\program files\microsoft visual studio 8\vc\atlmfc\include\atltime.h(394) : error C3861: 'strftime': identifier not found
    c:\program files\microsoft visual studio 8\vc\atlmfc\include\atltime.h(420) : error C3861: '_gmtime64_s': identifier not found
    c:\program files\microsoft visual studio 8\vc\atlmfc\include\atltime.h(421) : error C3861: 'strftime': identifier not found
    c:\program files\microsoft visual studio 8\vc\atlmfc\include\atlcomtime.h(363) : error C3861: 'strftime': identifier not found

    I don't know why they appear or how to make them go away. Does anybody have a clue what might be going on? Behind every great black man...             ... is the police. - Conspiracy brother Blog[^]

    B 1 Reply Last reply
    0
    • B Bob Stanneveld

      Hello, I'm developing an application using Visual Studio 2005. I use MFC and eveything was working (the prototypes, the application layer, eveything) until I set up the integration project. Everything compiled with a lot of warnings. I fixed them (mostly deprecated warnings that I suppress using the _CRT_SECURE_NO_DEPRECATE define). After fixing the warnings, errors stared to appead from every GUI file it was compiling. The 5 errors that keep coming back are:

      c:\program files\microsoft visual studio 8\vc\atlmfc\include\atltime.h(393) : error C3861: '_localtime64_s': identifier not found
      c:\program files\microsoft visual studio 8\vc\atlmfc\include\atltime.h(394) : error C3861: 'strftime': identifier not found
      c:\program files\microsoft visual studio 8\vc\atlmfc\include\atltime.h(420) : error C3861: '_gmtime64_s': identifier not found
      c:\program files\microsoft visual studio 8\vc\atlmfc\include\atltime.h(421) : error C3861: 'strftime': identifier not found
      c:\program files\microsoft visual studio 8\vc\atlmfc\include\atlcomtime.h(363) : error C3861: 'strftime': identifier not found

      I don't know why they appear or how to make them go away. Does anybody have a clue what might be going on? Behind every great black man...             ... is the police. - Conspiracy brother Blog[^]

      B Offline
      B Offline
      Bob Stanneveld
      wrote on last edited by
      #2

      I don't know why I solve problems just after posting a message here, but it happens everytime I post a problem. Don't get me wrong, but I try several hours if not days before I post a new thread here, but just after that, I find the solution. The problem was that I have a file called "time.h". This is not the real problem. I specified additional include directories and the MFC file includes <time.h>. The additional include directories cause the compiler to include my time.h instead of the right time.h (the C header). I don't know why my directories have precedance over the standard directories, but I think that MS would say: "This is by design.." Behind every great black man...             ... is the police. - Conspiracy brother Blog[^]

      D 1 Reply Last reply
      0
      • B Bob Stanneveld

        I don't know why I solve problems just after posting a message here, but it happens everytime I post a problem. Don't get me wrong, but I try several hours if not days before I post a new thread here, but just after that, I find the solution. The problem was that I have a file called "time.h". This is not the real problem. I specified additional include directories and the MFC file includes <time.h>. The additional include directories cause the compiler to include my time.h instead of the right time.h (the C header). I don't know why my directories have precedance over the standard directories, but I think that MS would say: "This is by design.." Behind every great black man...             ... is the police. - Conspiracy brother Blog[^]

        D Offline
        D Offline
        David Crow
        wrote on last edited by
        #3

        Bob Stanneveld wrote: I don't know why my directories have precedance over the standard directories... It all depends on the form used: #include "time.h" -- The preprocessor first looks for the file in the same directory of the file that contains the #include statement. #include <time.h> -- The preprocessor first looks for the file along the path specified by the /I compiler option.


        "Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

        B 1 Reply Last reply
        0
        • D David Crow

          Bob Stanneveld wrote: I don't know why my directories have precedance over the standard directories... It all depends on the form used: #include "time.h" -- The preprocessor first looks for the file in the same directory of the file that contains the #include statement. #include <time.h> -- The preprocessor first looks for the file along the path specified by the /I compiler option.


          "Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

          B Offline
          B Offline
          Bob Stanneveld
          wrote on last edited by
          #4

          DavidCrow wrote: #include "time.h" -- The preprocessor first looks for the file in the same directory of the file that contains the #include statement. #include -- The preprocessor first looks for the file along the path specified by the /I compiler option. I know that, but I don't know why an MFC library file includes my Time.h file using the #include <time.h> directive. I thought that directive tells the compiler to look first in the INCLUDE environment variable. Guess it does not. Behind every great black man...             ... is the police. - Conspiracy brother Blog[^]

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups