The other area you will have major problems with besides the settings, is
the library code, the library entries use absolute path for every file
name...  This won't work at all for portable builds (you are
virtually guaranteed to have different drive letters between different PCs).

Another area is if you build via MSVC you will have MSVC redistributable
runtime deps.  The mingw builds don't suffer from this though.

Sean wrote:

> docume~1\user\locals~1\applic~1\mixxx
>

Yeah, I'm old enough to know of the file mangling thing (3.1 -> 95.. you
start me up!), but I avoid it like the plague, there's almost always another
way to do something that doesn't rely on that...  but more then that I
really wanted to know if I would be able to pass in string constants with
spaces in them for stuff later, and it appears you can if you follow the
first example in the quoted mail, outside double quoting the define:
Rohan McGovern of Qt Software wrote:
>
> You can try it this way.  Leave out the quotes from the define, which means
> you'll be defining a bareword instead of a string:
>

> DEFINES += "_SETTINGS_PATH=Local\ Settings/Application\ Data/Mixxx/"
>

> Note, the outer double quotes are to let _qmake_ know it's all one
> argument, and the backslashes before the spaces are to let _make_ know it's
> all one argument.
>

> Then stringify it in your source:
>

> #define __STRINGIFY(x) #x
>
#define _STRINGIFY(x) __STRINGIFY(x)
>
#define SETTINGS_PATH _STRINGIFY(_SETTINGS_PATH)
>

> I don't know if that works with all compilers.
>

              __
--- == __/ t.O ==--
http://stacktrace.org/


On Mon, Mar 2, 2009 at 2:50 PM, Sean M. Pappalardo <[email protected]
> wrote:

>
>
> Garth Dahlstrom wrote:
>
>> if you change the _'s to spaces like they should be...  you get all kinds
>> of problems between qmake, make and windows escaping...  and
>>
>
> Incase it helps, you can use spaces in strings on the Windows command line
> just by quoting the string, e.g.
>
> cd "Documents and Settings\User\Local Settings\Application Data\Mixxx"
>
> as opposed to cd docume~1\user\locals~1\applic~1\mixxx
>
> (Or you could technically use the short names but that's not correct and
> will fail if someone has another long folder name that begins with "Locals"
> in their profile dir. (Since Local Settings could very well be locals~2)
>
> Sean
>
>
> <<--------------------------------------------------------------------------------->>
> This E-Mail message has been scanned for viruses
> and cleared by >>SmartMail<< from Smarter Technology, Inc.
>
> <<--------------------------------------------------------------------------------->>
>
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to