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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. COM
  4. Difference in the compiling modes

Difference in the compiling modes

Scheduled Pinned Locked Moved COM
questionannouncement
3 Posts 2 Posters 1 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.
  • L Offline
    L Offline
    Logan from Singapore
    wrote on last edited by
    #1

    Hi, Can someone tell me what is the difference between compiling in the following mode?? Win32 Release MinSize Win32 Release MinDependency Win32 Unicode Release MinSize Win32 Unicode Release MinDependency Thanks in advance

    S 1 Reply Last reply
    0
    • L Logan from Singapore

      Hi, Can someone tell me what is the difference between compiling in the following mode?? Win32 Release MinSize Win32 Release MinDependency Win32 Unicode Release MinSize Win32 Unicode Release MinDependency Thanks in advance

      S Offline
      S Offline
      Steve S
      wrote on last edited by
      #2

      They are all different; Win32 vs Win32 Unicode The code is built with either _UNICODE and UNICODE defined (the latter), or not (the former), which generally means using wide versions of system APIs, etc, except where explicit calls are made. Unicode apps won't run on W9x/ME systems, unless you're also using the MSLU. MinSize and Mindependency will also alter the way it's compiled. Mindependency means it relies on almost nothing else at install/runtime, so will often cause non-dll versions of libraries to be linked in, which may result in a larger app and a bigger footprint. Minsize does the reverse, and will use DLL versions of things like the CRT, which will give you a smaller app, and for apps that use DLL components which also use DLL versions of libraries, a smaller footprint. This is somewhat simplified. :) Steve S Developer for hire!

      L 1 Reply Last reply
      0
      • S Steve S

        They are all different; Win32 vs Win32 Unicode The code is built with either _UNICODE and UNICODE defined (the latter), or not (the former), which generally means using wide versions of system APIs, etc, except where explicit calls are made. Unicode apps won't run on W9x/ME systems, unless you're also using the MSLU. MinSize and Mindependency will also alter the way it's compiled. Mindependency means it relies on almost nothing else at install/runtime, so will often cause non-dll versions of libraries to be linked in, which may result in a larger app and a bigger footprint. Minsize does the reverse, and will use DLL versions of things like the CRT, which will give you a smaller app, and for apps that use DLL components which also use DLL versions of libraries, a smaller footprint. This is somewhat simplified. :) Steve S Developer for hire!

        L Offline
        L Offline
        Logan from Singapore
        wrote on last edited by
        #3

        Thanks for the reply. One of the few good reply I had read. There are too many replies in this forum that never asks the questions.

        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