×

Discussion Board

Results 1 to 4 of 4
  1. #1
    Registered User
    Join Date
    Jul 2003
    Posts
    32

    Directory confusion on Carbide C++ Pro

    I've a project including several modules that have implementations depending on OS versions. These implementations are organised through separated folders:

    My Module / S60_V80 / src
    / prj
    / ...
    / S60_V91 / src
    / prj
    / ...

    According to this organization, a same object can appear in two different directories with two different implementations:
    S60_V80 / src / My Object.cpp
    S60_V91 / src / My Object.cpp

    However, thanks to project files, there should not be any confusion between the implementations, as they are refered through relative paths from the MMP file.

    Unfortunately, Carbide C++ is confused by this architecture and seems to look for CPP files with the root directory instead of using relative paths from the MMP file. Therefore, it compiles the object "S60_V80 / src / My Object.cpp" while using the MMP file "S60_V91 / prj / My Project.mmp".

    Does anyone have a solution to this problem?

  2. #2
    Registered User
    Join Date
    Mar 2003
    Posts
    41

    Re: Directory confusion on Carbide C++ Pro

    Does this thread answer to your problem: http://discussion.forum.nokia.com/fo...errerid=135255

  3. #3
    Registered User
    Join Date
    Jul 2003
    Posts
    32

    Re: Directory confusion on Carbide C++ Pro

    Thanks for your answer, but unfortunately it does not answer to my question.

    My problem is that importing a "bld.inf" file within Carbide C++ and selecting the right "MMP" file does not have any consequence on the "CPP" files selected by Carbide C++ and that it takes files with the same names from other directories.

  4. #4
    Nokia Developer Expert
    Join Date
    Dec 2004
    Location
    Austin, TX
    Posts
    399

    Re: Directory confusion on Carbide C++ Pro

    If you copy your files to the workspace during import does this solve your problem?

    The other alternative (and I presume this is a linked import problem) is to go and exclude the files it should not be building manually. Right click on said files you don't want to build and select Properties > C/C++ Build > Exclude From Build.

    This shouldn't be a problem under Carbide 1.2.

    Tim

Similar Threads

  1. Carbide Pro, APP Trk, wont set debug point
    By jimgilmour1 in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 3
    Last Post: 2008-06-26, 06:05
  2. Importing mmp files in carbide 1.1 Pro
    By pgane in forum Symbian Tools & SDKs
    Replies: 3
    Last Post: 2007-06-22, 07:28
  3. REcmt APIs & Carbide PRO
    By mikfi in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 6
    Last Post: 2006-11-14, 18:20
  4. Importing existing project in Carbide c++ Pro doesn't work
    By svdwal in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 0
    Last Post: 2006-10-20, 14:54
  5. Carbide installation directory
    By qtyuli in forum Tools and SDK Feedback (Closed)
    Replies: 1
    Last Post: 2006-07-21, 01:28

Posting Permissions

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