visualc
asked on
Link settings problem
Hi everybody!
I'm working with VC5++ prof. edition.
In the link->customize settings the inccremental link option is checked, but the compiler "forget " this any time I build the project. Another problem is, that after compiling, when I try to run the application (no matter if in debug or in release mode), the compiler tell me, that some files (.obj files and the .exe file) doesn't exist, and ask me if I want to build them. If I choose no, and I run tha new .exe, everithyng is fine. This is happen only at two workspaces, which are from another PC.
HELP!!!!
I'm working with VC5++ prof. edition.
In the link->customize settings the inccremental link option is checked, but the compiler "forget " this any time I build the project. Another problem is, that after compiling, when I try to run the application (no matter if in debug or in release mode), the compiler tell me, that some files (.obj files and the .exe file) doesn't exist, and ask me if I want to build them. If I choose no, and I run tha new .exe, everithyng is fine. This is happen only at two workspaces, which are from another PC.
HELP!!!!
Hi,
for the compilator alert, have the same trouble. After some research, I can find that when you compil your prog in the small laps of time, the date of some file is not change, and you want to run it's appear older than the source code, so visual ask for build them. I can't find any solution. If you have one, please foward me.
for the compilator alert, have the same trouble. After some research, I can find that when you compil your prog in the small laps of time, the date of some file is not change, and you want to run it's appear older than the source code, so visual ask for build them. I can't find any solution. If you have one, please foward me.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>It happenes because the other PC you brought files from has different time and date settings . Be sure to change modificatino times for all the files you brought from that PC
Nah.. that's not it at all. It happens all the time since Microsoft went to version 5. It's got a lot to do with once it compiles, the time that is recorded in the .obj isn't in the past, but the current time. Then during the compile, it's checking for time LESS than the current time.
Phillip
Nah.. that's not it at all. It happens all the time since Microsoft went to version 5. It's got a lot to do with once it compiles, the time that is recorded in the .obj isn't in the past, but the current time. Then during the compile, it's checking for time LESS than the current time.
Phillip
VisualC , I am sure that it is the problem (see my answer ) - just reopen the source files
and save them with your date settings and then rebuild all once .
To see that i am right - you can first change your time settings to match the other computer you brought files from and see what happenes when you just "build".
and save them with your date settings and then rebuild all once .
To see that i am right - you can first change your time settings to match the other computer you brought files from and see what happenes when you just "build".
I'm not disagreeing with that fact. Makefiles have been plagued by the date inconsistencies since the dawn of time.
Visual C 5 and 6 have a NEW problem. You can be on your own machine and change a file. Compile the project, it picks up the edited file and compiles it correctly due to the time stamp. Run the program and it will complain that it needs to compile that same file. If compiled AGAIN, then it won't complain.
It's a weird one.
Of course, we're both just guessing at which one of these situations is his problem at this time.
Phillip
Visual C 5 and 6 have a NEW problem. You can be on your own machine and change a file. Compile the project, it picks up the edited file and compiles it correctly due to the time stamp. Run the program and it will complain that it needs to compile that same file. If compiled AGAIN, then it won't complain.
It's a weird one.
Of course, we're both just guessing at which one of these situations is his problem at this time.
Phillip
ASKER
Hi, guys!
Maizlish have right in my situation. I don't know why, but after the files transfer from the "old" to the '"new" PC, the "Latst Modify" time data of many of this was changed to the next mounth, even if the time settings of the "old" machine was O.K.
Now everithyng is working fine...
Thanks for your effort, and if ytou want, send your comments.
After two days I will lock this question giving the point to Maizlish!
Best regards, Tibi
Maizlish have right in my situation. I don't know why, but after the files transfer from the "old" to the '"new" PC, the "Latst Modify" time data of many of this was changed to the next mounth, even if the time settings of the "old" machine was O.K.
Now everithyng is working fine...
Thanks for your effort, and if ytou want, send your comments.
After two days I will lock this question giving the point to Maizlish!
Best regards, Tibi
Maizlish, my fullest apologies!
As far as the compiler is concerned, Cheer up! It's not you. I get it too.
Phillip