#133049 - code-g - Mon Jul 02, 2007 10:25 pm
| Code: |
------ Rebuild All started: Project: TestDS, Configuration: Release Win32 ------
Performing Makefile project actions
basename: too many arguments
Try `basename --help' for more information.
Cleaning...
/bin/sh.exe: [: too many arguments
make[1]: *** /c/Documents: Invalid request code. Stop.
make: *** [build] Error 2
Build log was saved at "file://c:\Documents and Settings\Anthony Crognale\My Documents\Visual Studio 2005\Projects\TestDS\TestDS\Release\BuildLog.htm"
TestDS - 0 error(s), 0 warning(s)
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ========== |
Can anyone explain to me what needs to be fixed?[/code]
_________________
Visit Ds Life at http://ds-life.blogspot.com/
#133050 - Lick - Mon Jul 02, 2007 10:29 pm
The path may not contain spaces.
_________________
http://licklick.wordpress.com
#133052 - tondopie - Mon Jul 02, 2007 10:37 pm
make directory on the root or something called 'ndsdev' and use that
#133053 - code-g - Mon Jul 02, 2007 10:41 pm
For the project directory? I'll try that! Thank you ;)
EDIT: It worked! Thanks so much :)
_________________
Visit Ds Life at http://ds-life.blogspot.com/
#133181 - Dood77 - Tue Jul 03, 2007 11:21 pm
Would %20 work as a space? :-/
_________________
If I use a term wrong or something then feel free to correct, I?m not much of a programmer.
Original DS Phat obtained on day of release + flashme v7
Supercard: miniSD, Kingston 1GB, Kingston 2GB
Ralink chipset PCI NIC
#133183 - mml - Tue Jul 03, 2007 11:35 pm
No, that won't help. That's for URL's.
You can *sometimes* get around the space problems with careful use of double quotes in the right places, but Windows' command driven bits arent particularly clever in their quote handling. It's amusing that the system least suited for dealing with spaces in file paths is also the one that uses them the most.
#133258 - tepples - Wed Jul 04, 2007 8:52 pm
Microsoft's party line:
On Windows, you're not supposed to make command-line components. You're supposed to make COM components.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#133293 - wintermute - Thu Jul 05, 2007 1:39 am
| tepples wrote: |
Microsoft's party line:
On Windows, you're not supposed to make command-line components. You're supposed to make COM components. |
citation needed.
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog
#133336 - tepples - Thu Jul 05, 2007 1:28 pm
I have no citation of a specific deprecation of the command prompt. But given Microsoft's attitude when it was pushing ActiveX (forget web browsers for now and concentrate only on the local machine), it appears that since Windows 98, programs for Windows are expected to offer OLE Automation hooks for use with Active Scripting, just as apps for Mac since Mac OS 7 are expected to offer Apple Events hooks for use with AppleScript. It appears that in the One Microsoft Way, "batch files" and "shell scripts" are a legacy technology inherited from MS-DOS-compatible and UNIX-compatible subsystems, deprecated since Windows 2000 by Windows Script Host. To get an idea of where Microsoft is going with this, look at Windows PowerShell, the command line replacement for Windows XP and newer, which is object-oriented more than the text-stream-oriented classic shell scripts.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.