X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=VjWVOsN8wTaBluodaG0gW38VABbcsoTIvonEFuOy40g=; b=HwZyXZ5bodB1H/J5m5vnR1L6/o07Md4mVU5WuRHKRoRPxaKd5zXS3NoFviSwDyuVt+ 9VW+3HFWEGavetgLbFHqaGKY/mav3Ep2kPoTpMmeSkibLdxP/+/I49ArurZwAWhXLg+X v9W8qzJi+EaCH++gv5uBnfQXCQjdk9L+mL0HM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=Aw4cx4+tzqG3B85KGeA4sXh/xSBiBrEdSqMbbBGck/2G1LhQY/R9oDjRASJsYXK5Ht Z5xAvvDtp42D8+HVVz2tHQlYQiOLltK5T3uo3pgE0m/4N5qNEZaE88EOKV7B5a9lwunt gp+wtpghMu5lyso5Rfnp+OzEOoEVU/jrQz6Eo= Message-ID: <1a5a6bfe0807141819k1be2f925nbfb67374b4c2231@mail.gmail.com> Date: Mon, 14 Jul 2008 21:19:58 -0400 From: "Daniel Verkamp" Sender: daniel DOT verkamp AT gmail DOT com To: djgpp AT delorie DOT com Subject: Re: Drag and Drop to Command Line In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 151364bc74fe82e9 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, Jul 14, 2008 at 3:09 PM, Rob Gaddi wrote: > Hi all -- > > This is probably an idiot newbie question, but if I Googled with it any > longer I was going to have to buy it dinner, so I'm hoping someone here > might have a suggestion/idea of what's going on. > > I've written a very short assembler in C for a proprietary microengine that > I'm working on. Like any sensible assembler, it wants to take in the input > filename on the command line, and if no further command line options are > given, make some assumptions based on the input filename as to what the > output filename should be. I drive it from the command prompt and all is > well. I pass it long filenames, it works with long filenames, and creates > outputs with long filenames. Fine, perfect, all well and good. > > But when I try to drag and drop from Explorer (under XP) onto the .EXE of > the interpreter, for some reason it gets passed the short file name instead, > and I get the appropriately mangled output file names. Ideally, this > wouldn't happen; Windows seems happy to pass plenty of other programs long > names from a drag and drop. But it thinks that mine wants a short name > instead. > > Any ideas on why this is happening and how to fix it? Is there some arcane > setting in the .PIF file that I'm missing? Some pragma flag that I should > be setting to tell Windows that I'm a sensible, modern sort of program, and > happy to take more than 11 characters of file name? > > Thanks in advance, > Rob > The short answer is "write a Windows program." DJGPP produces DOS executables. MinGW and Cygwin are two GCC ports for Windows, and if your code doesn't do anything unreasonably unportable, it should be relatively painless to recompile with one of them.