>
> Yes, power shell has improved, and it does support wildcarding, but I'm
> not sure how to use power shell instead of cmd... Also, I'm using mingw-w64
> as I have a 64 bit machine. I'm pretty sure this is slightly different than
> mingw. Do you think this has a factor?
I'm not that great with CMake (or C++ for that matter), but from what I can
see comparing our build_ming32
<https://github.com/LMMS/lmms/blob/stable-1.1/build_mingw32> and
build_ming64 <https://github.com/LMMS/lmms/blob/stable-1.1/build_mingw32>
scripts
and Toolchain files Win32Toolchain.cmake
<https://github.com/LMMS/lmms/blob/stable-1.1/cmake/modules/Win32Toolchain.cmake>
and Win64Toolchain.cmake
<https://github.com/LMMS/lmms/blob/stable-1.1/cmake/modules/Win64Toolchain.cmake>
for Linux, I think they are very similar.
I chose 32-bit because it's slightly more prominent historically, but I
would expect our instructions or scripts to address both platform in the
long term.
I never had to go searching for pkg-config...
Yeah it seems there are many packages which you already had. I'm not sure
why, but I'm writing mine from scratch, so if you got them via other means,
that could affect our results.
On a semi-related note, what I'm quite confused about is this "mingw-get
*PACKAGENAME*" stuff I keep reading... The mingw package manager doesn't
have a search option and the packages listed don't seem to be those we
need, which is adding a lot of time to getting the prereqs setup (hence the
initial thought to go Cygwin in our early emails)
- [email protected]
On Wed, Dec 24, 2014 at 4:26 PM, Samuel Xifaras <[email protected]>
wrote:
> Yes, power shell has improved, and it does support wildcarding, but I'm
> not sure how to use power shell instead of cmd... Also, I'm using mingw-w64
> as I have a 64 bit machine. I'm pretty sure this is slightly different than
> mingw. Do you think this has a factor? I never had to go searching for
> pkg-config...
>
> On Dec 24, 2014, at 4:18 PM, Tres Finocchiaro <[email protected]>
> wrote:
>
> > I saw many errors where *.extension did not exist.
>
>
> It certainly isn't as robust as unix is, but "dir *.extension" should work
> fine, although this may be "dir" doing the wildcarding, not the command
> interpreter, I don't know.
>
> I'm pretty sure I've done things like "cd C:\my_directory*" and it has
> successfully switched to "C:\my_directory_name" without issues, but again,
> this may be an edge case.
>
> I'm certain that PowerShell has improved in this area, so that might be a
> good start. I was pretty frustrated that the msys wasn't compatible with
> cmake out of the box (perhaps there is a way to workaround that, which
> could also solve the problem?)
>
> Unfortunately I was unable to catch up with you today... I got stuck on
> pkg-config, had to download and install it manually (which I did) and never
> got any further...
>
> Thanks for the update.
>
> -Tres
>
> - [email protected]
>
> On Wed, Dec 24, 2014 at 3:57 PM, Samuel Xifaras <[email protected]>
> wrote:
>
>> After carefully examining the errors produced while attempting to build
>> in visual studio, I think I've determined the one major issue:
>>
>> The windows command interpreter is stupid and doesn't support wild cards
>> in its file paths :/
>>
>> I'm pretty sure this is the underlying problem, because I saw many errors
>> where *.extension did not exist.
>>
>> This is frustrating. Do you know of a possible solution to this?
>>
>> On Dec 23, 2014, at 11:51 PM, Tres Finocchiaro <
>> [email protected]> wrote:
>>
>>
>> On Dec 23, 2014 11:16 PM, "Samuel Xifaras" <[email protected]> wrote:
>> >
>> > I ended up installing the windows version of cmake, and got it to
>> finish configuring, although there are a lot of tricky steps involved (I
>> wrote them down ;). And cmake has produced a visual studio solution file
>> that I can open. Now the challenge has been getting that to build. Though I
>> think i have solved that problem (I had to set a variable in CMakeCache
>> that would cause bin2res to be natively built). I have also tried getting
>> cmake to generate a Makefile, but I could not manage that unfortunately.
>> >
>> > Hopefully this will all work out and allow windows developers to join
>> the project!
>> >
>> > Sam
>> >
>> >
>>
>> Interested in reading your notes. :)
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming! The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is
>> your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>> look and join the conversation now. http://goparallel.sourceforge.net
>>
>> _______________________________________________
>> LMMS-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>>
>>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
>
> _______________________________________________
> LMMS-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
