Re: [avrdude-dev] Building in AVRDUDEWindows

avrdude-dev

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avrdude-dev] Building in AVRDUDEWindows

From:	Jason Hecker
Subject:	Re: [avrdude-dev] Building in AVRDUDEWindows
Date:	Thu, 21 Jul 2011 23:36:02 +1000

> But if you build this in MinGW, then there's no Cygwin DLL involved, and it 
> makes it easier to redistribute the executable (i.e. share your program with 
> others).

Interestingly v5.10 comes with the latest AVR Windows GCC tools.  Now,
it seems to use libusb0.dll.

$ cygcheck avrdude.exe
Found: C:\Program Files (x86)\Atmel\AVR Tools\AVR Toolchain\bin\avrdude.exe
C:\Program Files (x86)\Atmel\AVR Tools\AVR Toolchain\bin\avrdude.exe
  C:\Program Files (x86)\Atmel\AVR Tools\AVR Toolchain\bin\libusb0.dll
    C:\Windows\system32\ADVAPI32.DLL
      C:\Windows\system32\msvcrt.dll
        C:\Windows\system32\KERNELBASE.dll
          C:\Windows\system32\ntdll.dll
        C:\Windows\system32\API-MS-Win-Core-Console-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-DateTime-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Interlocked-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-WIN-Service-Core-L1-1-0.dll
      C:\Windows\system32\API-MS-WIN-Service-winsvc-L1-1-0.dll
      C:\Windows\system32\API-MS-WIN-Service-Management-L1-1-0.dll
      C:\Windows\system32\API-MS-WIN-Service-Management-L2-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LocalRegistry-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
      C:\Windows\system32\KERNEL32.dll
        C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\RPCRT4.dll
        C:\Windows\system32\SspiCli.dll
          C:\Windows\system32\CRYPTBASE.dll
            C:\Windows\system32\API-MS-Win-Core-DelayLoad-L1-1-0.dll
          C:\Windows\system32\API-MS-Win-Security-LSALookup-L1-1-0.dll
    C:\Windows\system32\cfgmgr32.dll
    C:\Windows\system32\setupapi.dll
      C:\Windows\system32\GDI32.dll
        C:\Windows\system32\USER32.dll
        C:\Windows\system32\LPK.dll
          C:\Windows\system32\USP10.dll
      C:\Windows\system32\OLEAUT32.dll
        C:\Windows\system32\ole32.dll
      C:\Windows\system32\DEVOBJ.dll

On the other hand the one I just built uses hid.dll.  Something smells fishy.

C:\temp\av\avrdude\avrdude.exe
  C:\Windows\system32\hid.dll
    C:\Windows\system32\msvcrt.dll
      C:\Windows\system32\KERNELBASE.dll
        C:\Windows\system32\ntdll.dll
      C:\Windows\system32\API-MS-Win-Core-Console-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-DateTime-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Interlocked-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
  C:\Windows\system32\setupapi.dll
    C:\Windows\system32\CFGMGR32.dll
      C:\Windows\system32\RPCRT4.dll
        C:\Windows\system32\API-MS-Win-Core-LocalRegistry-L1-1-0.dll
        C:\Windows\system32\SspiCli.dll
          C:\Windows\system32\CRYPTBASE.dll
            C:\Windows\system32\API-MS-Win-Core-DelayLoad-L1-1-0.dll
          C:\Windows\system32\API-MS-Win-Security-LSALookup-L1-1-0.dll
      C:\Windows\system32\ADVAPI32.dll
        C:\Windows\system32\API-MS-WIN-Service-Core-L1-1-0.dll
        C:\Windows\system32\API-MS-WIN-Service-winsvc-L1-1-0.dll
        C:\Windows\system32\API-MS-WIN-Service-Management-L1-1-0.dll
        C:\Windows\system32\API-MS-WIN-Service-Management-L2-1-0.dll
    C:\Windows\system32\GDI32.dll
      C:\Windows\system32\USER32.dll
      C:\Windows\system32\LPK.dll
        C:\Windows\system32\USP10.dll
    C:\Windows\system32\OLEAUT32.dll
      C:\Windows\system32\ole32.dll
    C:\Windows\system32\DEVOBJ.dll


No nasty Cygnus DLLs in either though.  Alright, next step... libusb
and libftdi for Windows needs to be installed and I'll see if I can
build it then.

[Prev in Thread]

Current Thread

[Next in Thread]

[avrdude-dev] Building in AVRDUDEWindows, Jason Hecker, 2011/07/21
- Re: [avrdude-dev] Building in AVRDUDEWindows, Joerg Wunsch, 2011/07/21
  - Re: [avrdude-dev] Building in AVRDUDEWindows, Jason Hecker, 2011/07/21
    - Re: [avrdude-dev] Building in AVRDUDEWindows, Weddington, Eric, 2011/07/21
    - Re: [avrdude-dev] Building in AVRDUDEWindows, Jason Hecker <=

Prev by Date: Re: [avrdude-dev] Building in AVRDUDEWindows
Next by Date: [avrdude-dev] [bug #33811] Parallel make fails
Previous by thread: Re: [avrdude-dev] Building in AVRDUDEWindows
Next by thread: [avrdude-dev] [bug #33811] Parallel make fails
Index(es):
- Date
- Thread