Run the compiled exe appears, as shown in the title error status 0 xc000012f.
But the PBD in other projects can be used again,

CodePudding user response:

FULL - REBUILD the redistribution of a try,

In general, however, this kind of problem appeared in, multiple PBD is not the same programmer compile, or even though the same programmers, but they have compiled respectively in multiple projects and their release,

Project not good management, the project manager and technical director to play the fart fart,


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --


Problem is caused by, each object's statement is not consistent,

For example, in A project, w_1 function_1 statement is such function_1 (string A)
But in B engineering, for example, w_1 function_1 statement is such function_1 (a)

Each programmer to compile (even FULLL - REBUILD) is no problem, but their release have a problem:

C.p program of bd, thought lost a STRING to function_1 went, but d.p bd for a long,

Or perhaps the global variable declaration,

E.p bd in a global variable, but compile f.p bd projects not, call wrong, of course,


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

The above is just a convenience and simple example, practice a lot more complicated,

So, only one solution, specify a person responsible for the compilation, put everything together in a project,

Everybody cannot release their own, can only give the man the PBL, unified by him in a FULL - REBUILD project, the different statement can be found in the compilation process,

CodePudding user response:

May be the PBD references to other objects, you can use a full rebuild to try, if not, suggest you still use PBL included, to compile

CodePudding user response:

A compilation, FULLL - it's no problem for me to REBUILD many times, the same PBD in other project also does not have the prompt,