Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Make error, multiple target patterns
Forum Updated to NodeBB v4.3 + New Features

Make error, multiple target patterns

Scheduled Pinned Locked Moved General and Desktop
5 Posts 2 Posters 14.8k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    Thanatos.jsse
    wrote on last edited by
    #1

    I have a project that is composed by a main core, with three sub dirs that are building like "libraries":https://github.com/thanatosJSSE/Sipred/blob/Dev_Test/src/src.pro.

    @Makefile.module_mngr.Release:76: *** multiple target patterns. Stop.
    mingw32-make.exe[3]: *** [release] Error 2
    mingw32-make.exe[2]: *** [sub-module-module_mngr-pro-make_default-ordered] Error 2
    mingw32-make.exe[1]: *** [sub-managers-make_default-ordered] Error 2
    mingw32-make.exe: *** [sub-src-make_default-ordered] Error 2@

    I've looking in all forums and sources but I can't find a solution.

    1 Reply Last reply
    0
    • F Offline
      F Offline
      franku
      wrote on last edited by
      #2

      Look for \ and replace them with / in paths. Then re-run qmake. HTH?

      This, Jen, is the internet.

      1 Reply Last reply
      0
      • T Offline
        T Offline
        Thanatos.jsse
        wrote on last edited by
        #3

        Thank you franku.

        [quote author="franku" date="1343423995"]Look for \ and replace them with / in paths. Then re-run qmake. HTH?[/quote]

        I don't have "" in my pro files, but the make files output have strange lines:
        @# Makefile Debug
        SOURCES = ........\Sipred\src\managers\module\modulemngr.cpp
        ........\Sipred\src\managers\module\moduleinfo.cpp debug\moc_moduleinfo.cpp
        debug\moc_modulemngr.cpp
        OBJECTS = debug/modulemngr.o
        debug/moduleinfo.o
        debug/moc_moduleinfo.o
        debug/moc_modulemngr.o
        DIST =
        QMAKE_TARGET = modulemanagerd
        DESTDIR = "c:\Documents and Settings\dismet\Desktop\Sipred\Sipred-Debug\lib" #avoid trailing-slash linebreak
        TARGET = modulemanagerd.dll
        DESTDIR_TARGET = "c:\Documents and Settings\dismet\Desktop\Sipred\Sipred-Debug\libmodulemanagerd.dll"@

        I think the problem is in generated Makefile.

        1 Reply Last reply
        0
        • F Offline
          F Offline
          franku
          wrote on last edited by
          #4

          bq. SOURCES = ........\Sipred\src\managers\module\modulemngr.cpp

          Did you re-run qmake? These paths are output during the qmake step into the makefiles.

          Are there any other .pro / .pri files included in any of your .pro files?

          This, Jen, is the internet.

          1 Reply Last reply
          0
          • T Offline
            T Offline
            Thanatos.jsse
            wrote on last edited by
            #5

            [quote author="franku" date="1343462836"]bq.

            Did you re-run qmake? These paths are output during the qmake step into the makefiles.

            Are there any other .pro / .pri files included in any of your .pro files?[/quote]

            1. Yes I did.
            2. I have several pro and pri files, but I was very careful to not use "" in paths. This is a search, looking for \

            !http://www.flickr.com/photos/thanatosjsse/7661552940/!

            PD: Can't attach an image, so here is the "link.":http://www.flickr.com/photos/thanatosjsse/7661552940/

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved