If you're really tight on space you can also use `--build=MinSizeRel` when
building with the sdk.
I probably wouldn't do that if you're paranoid about reliable builds as I
believe it disables some checks. Good for personal projects though.

On 3 September 2015 at 19:43, Brion Vibber <[email protected]> wrote:

> Indeed that'd be nice -- I recommend filing a request on the issue tracker
> so the idea's not forgotten: https://github.com/juj/emsdk/issues
>
> -- brion
>
> On Thu, Sep 3, 2015 at 11:33 AM, Robert Goulet <[email protected]
> > wrote:
>
>> I'll try that. But optionally we should still be able to automate this
>> with an option when we build, no?
>>
>> On Thursday, September 3, 2015 at 2:17:50 PM UTC-4, Brion Vibber wrote:
>>>
>>> It looks to me like you only need the files in the 'bin' subdir (eg
>>> clang/fastcomp/build_incoming_64/bin)... If you remove the rest of the
>>> build & src files, does it still work as expected?
>>>
>>> -- brion vibber (brion @ pobox.com / bvibber @ wikimedia.org)
>>>
>>> On Thu, Sep 3, 2015 at 11:01 AM, Robert Goulet <[email protected]>
>>> wrote:
>>>
>>>> I'm using the Windows binary package, and would like to be able to
>>>> produce the same small package without all the extra gigabytes of
>>>> intermediate build files.
>>>>
>>>> On Thursday, September 3, 2015 at 1:29:29 PM UTC-4, Brion Vibber wrote:
>>>>>
>>>>> Out of curiosity, are you folks building on Linux (where the SDK
>>>>> doesn't provide binary packages at all) or on Mac/Windows (where the SDK
>>>>> offers binary packages for releases, but not for the incoming branch)?
>>>>>
>>>>> I'd kinda like binary builds on Linux too, but I know compatibility
>>>>> across distributions tends to be a harder problem there.
>>>>>
>>>>> -- brion
>>>>>
>>>>> On Thu, Sep 3, 2015 at 10:09 AM, Robert Goulet <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> I would be interested to get a "clean" option as well, because
>>>>>> there's a huge difference in size between a binary package that we 
>>>>>> download
>>>>>> from your web page, versus a build that we do locally. Don't you have 
>>>>>> some
>>>>>> sort of automated script that we could use to package Emscripten on our
>>>>>> side?
>>>>>>
>>>>>>
>>>>>> On Tuesday, September 1, 2015 at 2:41:02 AM UTC-4, Sergey
>>>>>> Solozhentsev wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> I updated emscripten sdk using emsdk. I noticed that now it is built
>>>>>>> from sources. I do not need sources and debug info. Is any way to clear 
>>>>>>> all
>>>>>>> sources debug info object files etc? Only necessary files?
>>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "emscripten-discuss" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to [email protected].
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "emscripten-discuss" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "emscripten-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Aidan

Currently co-authoring a book on Docker -
http://docker-in-practice.github.io/

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to