Android SDK install path cannot contain spaces...



  • ...nuff said. Yay for basically being forced to pollute root of my hard drive.



  • Good old C:\PROGRA~1?



  • ...oh...
    ...would that still work?
    ...didn't even cross my mind 😕



  • You know a program is bad when you have to use MS-DOS compatibility hacks to run it.



  • Whatever you do, don't install it in /usr /bin/androidsdk



  • You can use dir /x to see the 8.3 mangled equivalents of spaceful filenames.



  • yeah... I didn't need this to know that android and java are bad...



    1. Luckily i'm not torturing myself by using linux

    2. The beginning sounds interesting, please continue



  • I don't have the link, but there's a famous commit on GitHub apologizing for an uninstall script that would remove the user's home directory. Looking at the space in @ben_lubar's post should give an idea as to what went wrong...


  • Dupa

    @LB_ said:

    uninstall script that would remove the user's home directory.

    Steam did that. Only it would remove the whole root if run as root. The reason why it only removed home was that no one sensible runs steam as root.



  • ahhh! I missed that 😃



  • Any reason you can't just put it in c:\stuff\android-sdk or something?

    edit: Or if you don't want to put any extra dirs in your root, c:\Users\[yourname]\android-sdk





  • The nice thing is that this could never happen on Windows because C:\Program Files \foo contains two spaces and C:\Program generally doesn't have anything important in it if it even exists.


  • Discourse touched me in a no-no place

    @ben_lubar said:

    and C:\Program generally doesn't have anything important in it if it even exists

    It usually has a subdirectory called Files


  • SockDev

    Only if you're undefined



  • @hungrier said:

    edit: Or if you don't want to put any extra dirs in your root, c:\Users[yourname]\android-sdk

    That was the default path which I wanted to change to program files. How does it make any sense to put SDK into user-specific folder? That's like putting your household's tools into your personal key-locked jewelry box



  • If you're the only one doing Android development, it's more like putting your own tools into your toolbox.



  • @hungrier said:

    Any reason you can't just put it in c:\stuff\android-sdk or something?

    edit: Or if you don't want to put any extra dirs in your root, c:\Users\[yourname]\android-sdk

    Because "yourname" is not guaranteed to not have a space? (Yes, at one point mine was "FirstName LastName")


  • Discourse touched me in a no-no place

    @dcon said:

    Because "yourname" is not guaranteed to not have a space? (Yes, at one point mine was "FirstName LastName")

    If the tools were non-shit, they wouldn't care. I mostly don't put spaces in directory names because I'm lazy when I'm typing them out, but I really don't like toolchains that get this wrong. Which does sometimes seem to be all of them… 😖

    It doesn't bother me quite enough for me to be foolish enough to write my own.



  • @hungrier said:

    Any reason you can't just put it in c:\stuff\android-sdk or something?

    How about it's not fucking 1986?

    @hungrier said:

    edit: Or if you don't want to put any extra dirs in your root, c:\Users[yourname]\android-sdk

    BECAUSE IT'S IMPOSSIBLE THAT YOUR NAME COULD HAVE A SPACE IN IT!

    Oh wait. Virtually everybody's name has a space in it. At least one. I guess unless you're Cher.



  • I would just put it on the root of C:\ and be done with it.



  • But then what would you complain about?



  • the lout that smashed my driver side wing mirror 😃


  • Winner of the 2016 Presidential Election

    @LB_ said:

    remove the user's home directory

    Not... the home directory... The /usr folder. Which... is worse since it's got a bunch of system-critical stuff.



  • Shouldn't /use have /us(e)r programs etc. In it?


  • Winner of the 2016 Presidential Election

    Unix System Resources, apparently. Also TIL.

    I knew it wasn't for user stuff though, it's a system directory that holds stuff like libraries and binaries



  • @blakeyrat said:

    Oh wait. Virtually everybody's name has a space in it. At least one. I guess unless you're Cher.

    ACTUALLY... thanks to that SDK setup, I've found out that for some reason (It's a recent system reinstall), even though my account has my full name, the user directory is "midni", which is truncation of my old account/user directory name, "Midnight". No idea when and why windows decided to do that.



  • Windows 10 will use a truncated account name if you create the account using a Microsoft account, so that may be it.


  • Discourse touched me in a no-no place

    @sloosecannon said:

    I knew it wasn't for user stuff though, it's a system directory that holds stuff like libraries and binaries

    I always thought of it as “place that holds programs that users run”. (So yes, TIL too.)



  • I basically gave up on Windows conventions at this point.

    All my linuxy dev tools go to C:\Util or C:\Dev.

    Documents also go into their own separate folder (or Google Drive), as User\Documents has become a dumping ground for every crappy video game or Windows program.



  • @sloosecannon said:

    Unix System Resources, apparently. Also TIL.

    I knew it wasn't for user stuff though, it's a system directory that holds stuff like libraries and binaries

    And it has such a great, intuitive, name. Obviously only a genius came up with it.

    And of course since it's Linux, the awful name is there to stay forever. Because nobody can ever change anything, ever. There's no APIs to look up the correct path, like in better OSes, so it's just wrong for all time.



  • @cartman82 said:

    I basically gave up on Windows conventions at this point.

    All my linuxy dev tools go to C:\Util or C:\Dev.

    As long as you're aware backup software won't back that shit up by default, because it's outside the normal folder tree.

    But sure, good solution. Give the fuck up. Fly the surrender flag. Let the morons running this shitty broken software win.



  • Why would I backup that shit? The only thing I backup are my projects and documents.


  • kills Dumbledore

    @blakeyrat said:

    Because nobody can ever change anything, ever

    Unfortunately, the same is true in Windows, given how many applications hardcode "C:\Program Files".

    It is a shitty name though. Where shall we put all the system resources? I know, somewhere that reads as "user"



  • @Jaloopa said:

    Unfortunately, the same is true in Windows, given how many applications hardcode "C:\Program Files".

    But at least in that case, those applications are clearly incorrect and buggy. In the Linux case, even correctly-written applications prevent it (changing the folder's name) from happening.

    @Jaloopa said:

    It is a shitty name though. Where shall we put all the system resources? I know, somewhere that reads as "user"

    Yeah; and go out of your way to do so by naming the folder after an OS you're not even running. "lsr" at least would sound like "loser", a good description of the average Linux user.

    BTW, imagine all the "micro$oft sucks!11!!!" jokes we'd get if the tables were turned, and Windows had an important folder named, "Macintosh System Resources".



  • @blakeyrat said:

    BTW, imagine all the "micro$oft sucks!11!!!" jokes we'd get if the tables were turned, and Windows had an important folder named, "Macintosh System Resources".

    We don't have to imagine very much. Windows puts all of its 64-bit system files into System32. And 32-bit stuff is now WoW64.


  • SockDev

    @boomzilla said:

    WoW64.

    Windows on Windows 64(bit)

    still a stupid name, but at least there's some semblence of thought there



  • @accalia said:

    @boomzilla said:
    WoW64.

    Windows on Windows 64(bit)

    still a stupid name, but at least there's some semblence of thought there

    I understand what they think they're saying, but it's backwards. That is 32-bit windows stuff, but there's no 32 in the name!


  • SockDev

    @boomzilla said:

    I understand what they think they're saying, but it's backwards.

    W32oW is a better name?

    bugger that for a game of soldiers!



  • @boomzilla said:

    We don't have to imagine very much. Windows puts all of its 64-bit system files into System32.

    Yup; due to broken applications.

    @boomzilla said:

    And 32-bit stuff is now WoW64.

    WoW stands for "Windows on Windows", or expanded out a bit: "Windows 32 on Windows 64". It's basically an emulation layer, allowing 64-bit Windows to behave like 32-bit Windows for compatibility with 32-bit apps.

    I agree the folder name is badly chosen, but people aren't supposed to be in there looking at it. Even developers. Unless you work for Microsoft, there's really no reason to touch or even think about that.

    Now that said, it's Windows, so people DO go way out of their way to fuck around with shit they shouldn't touch and end up breaking their own computers, then complain about Microsoft writing crappy software. But they shouldn't.

    @boomzilla said:

    I understand what they think they're saying, but it's backwards. That is 32-bit windows stuff, but there's no 32 in the name!

    Presumably, because when they were developing it at Microsoft, nobody said "Windows 32-bit", they just said "Windows". So Windows 64-bit had a name, but normal Windows had no equivalent name. Which means in conversation they'd say "Windows DLLs running on Windows 64". Which means the folder is named "Windows on Windows 64".

    But I'm just guessing there.

    The real point is: it could be called "Frogblast The Vent Core" for all it matters; it's Microsoft's business, you don't need to ever touch it nor should you.



  • @accalia said:

    W32oW is a better name?

    Only if you want a name that makes sense instead of one that has a snazzy sound. Though 32WoW is probably better on that front.

    @blakeyrat said:

    The real point is: it could be called "Frogblast The Vent Core" for all it matters; it's Microsoft's business, you don't need to ever touch it nor should you.

    How did I know you'd do a 180 on bad naming conventions and defend that bit of nonsense? Yes, I already knew all those reasons behind it. That doesn't make the names any better.



  • @boomzilla said:

    How did I know you'd do a 180 on bad naming conventions and defend that bit of nonsense? Yes, I already knew all those reasons behind it. That doesn't make the names any better.

    I already said the name was bad. What do you want? Skywriting?


  • Discourse touched me in a no-no place

    @boomzilla said:

    That doesn't make the names any better.

    There are two difficult things in computing:

    1. Cache management.
    2. Naming things.
    3. Off by one errors.


  • @dkf said:

    @boomzilla said:
    That doesn't make the names any better.

    There are two difficult things in computing:

    1. Cache management.
    2. Naming things.
    3. Off by one errors.

    And of those things, only Naming things is hard to solve.

    Oh, and undefined undefined undefined is up with Dsikroze anyway. How did 1, 2, 3 in the original message become previewed etc. as 1, 1, and 0 ?



  • something with a blank line after it

    1. three
    2. three
    3. three
    something with a blank line after it
    1. three
    2. three
    3. three

    Apparently DiscoOrderedListNumbering inside quotes is Different™



  • Oh good. We're talking about discourse bugs again.



  • @blakeyrat said:

    The real point is: it could be called "Frogblast The Vent Core" for all it matters; it's Microsoft's business, you don't need to ever touch it nor should you.

    👋 Hardware vendor here. We stuff things in those folders all the time due to authoring device drivers and user-mode hardware access APIs. Even our engineers get System32 and Syswow64 mixed up al the time. It's cnofusing as hell and I hav eto explain the difference about six times a month.

    Also Discourse is swallowing eystorkes and putting them out-of-order and I refuse to fix this post.



  • @Jaloopa said:

    @blakeyrat said:
    Because nobody can ever change anything, ever

    Unfortunately, the same is true in Windows, given how many applications hardcode "C:\Program Files".

    It is a shitty name though. Where shall we put all the system resources? I know, somewhere that reads as "user"


    Curiously, the "Program Files" thing is even more broken, historically, than you think.

    On Win7 and after (possibly on Vista - I never had that particular pain), Explorer aliases lots of system-like folder names to localised equivalents. So it's "C:\Program Files" always (except when you're running Win64, when it's "C:\Program Files (x86)" and "C:\Program Files"), but when you look at it in Explorer on a localised version (I'll use the French version, 'coz that's what I have), you see something like "C:\Programmes". On versions up to and including XP, it wasn't like that. If you had the localised versions, it localised the true names of the directories, so it really was "C:\Programmes". This, obviously, caused some amusement when localisation-challenged outfits tried to start distributing their software outside the English-speaking world.



  • @mott555 said:

    @blakeyrat said:
    The real point is: it could be called "Frogblast The Vent Core" for all it matters; it's Microsoft's business, you don't need to ever touch it nor should you.

    👋 Hardware vendor here. We stuff things in those folders all the time due to authoring device drivers and user-mode hardware access APIs. Even our engineers get System32 and Syswow64 mixed up al the time. It's cnofusing as hell and I hav eto explain the difference about six times a month.

    Also Discourse is swallowing eystorkes and putting them out-of-order and I refuse to fix this post.


    FFS dude, use the GDMF APIs that allow you to find out the correct names on the machine you're running the install on!


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.