×

Discussion Board

Results 1 to 3 of 3
  1. #1
    Registered User
    Join Date
    Oct 2003
    Posts
    6

    Probelm after building abld file on C++ , Symbian 60 series environment

    i Have configured all the thing s and built abld file with bldmake command but after that , there is probelm while doing the abld file

    when i type abld build wins udeb in windows 98

    C:\Symbian\6.1\Series60\Epoc32Ex\HelloWorld>bldmake bldfiles
    C:\Symbian\6.1\Series60\Epoc32Ex\HelloWorld>abld build wins udeb
    nmake -nologo -f "\Symbian\6.1\Series60\EPOC32\BUILD\SYMBIAN\6.1\SERIES60\EPOC32EX\HELLOWORLD\EXPORT.make" EXPORT VERBOSE=-s
    Bad command or file name
    nmake -nologo -f "\Symbian\6.1\Series60\EPOC32\BUILD\SYMBIAN\6.1\SERIES60\EPOC32EX\HELLOWORLD\WINS.make" MAKEFILE VERBOSE=-s
    Bad command or file name
    nmake -nologo -f "\Symbian\6.1\Series60\EPOC32\BUILD\SYMBIAN\6.1\SERIES60\EPOC32EX\HELLOWORLD\WINS.make" LIBRARY VERBOSE=-s
    Bad command or file name
    nmake -nologo -f "\Symbian\6.1\Series60\EPOC32\BUILD\SYMBIAN\6.1\SERIES60\EPOC32EX\HELLOWORLD\WINS.make" RESOURCE CFG=UDEB VERBOSE=-s
    Bad command or file name
    nmake -nologo -f "\Symbian\6.1\Series60\EPOC32\BUILD\SYMBIAN\6.1\SERIES60\EPOC32EX\HELLOWORLD\WINS.make" TARGET CFG=UDEB VERBOSE=-s
    Bad command or file name
    nmake -nologo -f "\Symbian\6.1\Series60\EPOC32\BUILD\SYMBIAN\6.1\SERIES60\EPOC32EX\HELLOWORLD\WINS.make" FINAL CFG=UDEB VERBOSE=-s
    Bad command or file name

  2. #2
    Regular Contributor
    Join Date
    Aug 2003
    Posts
    99
    hi! did u try the following commands?

    bldmake bldfiles
    abld makefile vc6
    abld build vc6

    then abld build wins udeb?

  3. #3
    Regular Contributor
    Join Date
    Sep 2003
    Location
    Bangalore,India.
    Posts
    63

    build problem solution

    Hi,

    Mr Whitemoon is mixing up the things. He is referring to both
    command line build and VC++ workspace build.

    Actually the phrase 'bad command or filename' means the previous command executed is not recognised by windows shell, in this case 'nmake' as I see from the text you have pasted.

    This is the problem with registering environment variables of VC++. This will be preferably done at VC++ installation time itself.

    Otherwise you have to run a script called 'vcvars32.bat' located
    somewhere in VC++ installation folder. Even if that doesn't work, you have to play around with windows System environment variables 'MSDevDir' and 'path'.

    This enables 'nmake' to be run from anywhere from the shell.

    Regards,
    Sreenivasulu Y

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •