On Wed, Jul 8, 2009 at 11:14 AM, nakro <[email protected]> wrote:
> > Pawel, since i have it working on my machine (or i really could not > code with chrome) > i can tell you it is much more than a flag > > just as an example the name of chrome_dll.vcproj produces chrome.dll, > but the incremental files would clash with chrome.vcproj who does the > exe This was fixed in the past by putting chrome.dll in the intermediary directory and hardlinking it afterward in the ouput directory. I don't know what happens with the GYP conversion. Before the conversion, only the single projects that failed to link on 32 bit OS had incremental linking disabled. I don't know why it was disabled for every projects afterward. Maybe Steven can shed some light on that. another example : you seem to have several 'TCMalloc_SystemAlloc' > functions, which the linker can resolve if they are in a lib > but would clash if linked as objects > > but none of this is too hard to solve, and i think is worth it.... About directly linking object files, it's just nobody taking the time to fix the remaining issues and enabling the flag. Patches are welcome. M-A --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
