How to connect ICU library with gcc in the Ubuntu 16.04?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite












I have downloaded the icu4c-61_1-Ubuntu16.04-x64.tgz from the http://site.icu-project.org/download/61#TOC-ICU4C-Download site. I do not see any installation instruction there. In my NetBeans C/C++ 'Ant Library Manager' the button 'New Library' and other fields are inactive - inaccessible. (In the NetBeans, C debugging works.)

In the filesystem, is there a directory where the unpacked library should be placed and/or a file where the information should be added? Thanks!







share|improve this question





















  • @muru: Please consider if the icu.project.org is not worth our attention enough to get its tag, that I have proposed. In fact, I am only trying it, but their site is generally recommended for solving problems with different language text coding. I intended to describe the proposed tag later. Thanks!
    – TomáÅ¡ Pečený
    Jun 7 at 6:29










  • Are the existing tags insufficient?
    – muru
    Jun 7 at 6:32










  • I feel the tag 'language' as too general and 'language-support' is described as 'the language support provided by Ubuntu'. I suggested the tag 'icu' as an analogy to the tag 'gcc' .
    – TomáÅ¡ Pečený
    Jun 7 at 6:43










  • And I replaced that with libraries, which is sufficiently general enough.
    – muru
    Jun 7 at 6:46










  • I agree, thanks!
    – TomáÅ¡ Pečený
    Jun 7 at 6:48














up vote
1
down vote

favorite












I have downloaded the icu4c-61_1-Ubuntu16.04-x64.tgz from the http://site.icu-project.org/download/61#TOC-ICU4C-Download site. I do not see any installation instruction there. In my NetBeans C/C++ 'Ant Library Manager' the button 'New Library' and other fields are inactive - inaccessible. (In the NetBeans, C debugging works.)

In the filesystem, is there a directory where the unpacked library should be placed and/or a file where the information should be added? Thanks!







share|improve this question





















  • @muru: Please consider if the icu.project.org is not worth our attention enough to get its tag, that I have proposed. In fact, I am only trying it, but their site is generally recommended for solving problems with different language text coding. I intended to describe the proposed tag later. Thanks!
    – TomáÅ¡ Pečený
    Jun 7 at 6:29










  • Are the existing tags insufficient?
    – muru
    Jun 7 at 6:32










  • I feel the tag 'language' as too general and 'language-support' is described as 'the language support provided by Ubuntu'. I suggested the tag 'icu' as an analogy to the tag 'gcc' .
    – TomáÅ¡ Pečený
    Jun 7 at 6:43










  • And I replaced that with libraries, which is sufficiently general enough.
    – muru
    Jun 7 at 6:46










  • I agree, thanks!
    – TomáÅ¡ Pečený
    Jun 7 at 6:48












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have downloaded the icu4c-61_1-Ubuntu16.04-x64.tgz from the http://site.icu-project.org/download/61#TOC-ICU4C-Download site. I do not see any installation instruction there. In my NetBeans C/C++ 'Ant Library Manager' the button 'New Library' and other fields are inactive - inaccessible. (In the NetBeans, C debugging works.)

In the filesystem, is there a directory where the unpacked library should be placed and/or a file where the information should be added? Thanks!







share|improve this question













I have downloaded the icu4c-61_1-Ubuntu16.04-x64.tgz from the http://site.icu-project.org/download/61#TOC-ICU4C-Download site. I do not see any installation instruction there. In my NetBeans C/C++ 'Ant Library Manager' the button 'New Library' and other fields are inactive - inaccessible. (In the NetBeans, C debugging works.)

In the filesystem, is there a directory where the unpacked library should be placed and/or a file where the information should be added? Thanks!









share|improve this question












share|improve this question




share|improve this question








edited Jun 6 at 23:56









muru

128k19269459




128k19269459









asked Jun 6 at 22:28









TomáÅ¡ Pečený

44051032




44051032











  • @muru: Please consider if the icu.project.org is not worth our attention enough to get its tag, that I have proposed. In fact, I am only trying it, but their site is generally recommended for solving problems with different language text coding. I intended to describe the proposed tag later. Thanks!
    – TomáÅ¡ Pečený
    Jun 7 at 6:29










  • Are the existing tags insufficient?
    – muru
    Jun 7 at 6:32










  • I feel the tag 'language' as too general and 'language-support' is described as 'the language support provided by Ubuntu'. I suggested the tag 'icu' as an analogy to the tag 'gcc' .
    – TomáÅ¡ Pečený
    Jun 7 at 6:43










  • And I replaced that with libraries, which is sufficiently general enough.
    – muru
    Jun 7 at 6:46










  • I agree, thanks!
    – TomáÅ¡ Pečený
    Jun 7 at 6:48
















  • @muru: Please consider if the icu.project.org is not worth our attention enough to get its tag, that I have proposed. In fact, I am only trying it, but their site is generally recommended for solving problems with different language text coding. I intended to describe the proposed tag later. Thanks!
    – TomáÅ¡ Pečený
    Jun 7 at 6:29










  • Are the existing tags insufficient?
    – muru
    Jun 7 at 6:32










  • I feel the tag 'language' as too general and 'language-support' is described as 'the language support provided by Ubuntu'. I suggested the tag 'icu' as an analogy to the tag 'gcc' .
    – TomáÅ¡ Pečený
    Jun 7 at 6:43










  • And I replaced that with libraries, which is sufficiently general enough.
    – muru
    Jun 7 at 6:46










  • I agree, thanks!
    – TomáÅ¡ Pečený
    Jun 7 at 6:48















@muru: Please consider if the icu.project.org is not worth our attention enough to get its tag, that I have proposed. In fact, I am only trying it, but their site is generally recommended for solving problems with different language text coding. I intended to describe the proposed tag later. Thanks!
– TomáÅ¡ Pečený
Jun 7 at 6:29




@muru: Please consider if the icu.project.org is not worth our attention enough to get its tag, that I have proposed. In fact, I am only trying it, but their site is generally recommended for solving problems with different language text coding. I intended to describe the proposed tag later. Thanks!
– TomáÅ¡ Pečený
Jun 7 at 6:29












Are the existing tags insufficient?
– muru
Jun 7 at 6:32




Are the existing tags insufficient?
– muru
Jun 7 at 6:32












I feel the tag 'language' as too general and 'language-support' is described as 'the language support provided by Ubuntu'. I suggested the tag 'icu' as an analogy to the tag 'gcc' .
– TomáÅ¡ Pečený
Jun 7 at 6:43




I feel the tag 'language' as too general and 'language-support' is described as 'the language support provided by Ubuntu'. I suggested the tag 'icu' as an analogy to the tag 'gcc' .
– TomáÅ¡ Pečený
Jun 7 at 6:43












And I replaced that with libraries, which is sufficiently general enough.
– muru
Jun 7 at 6:46




And I replaced that with libraries, which is sufficiently general enough.
– muru
Jun 7 at 6:46












I agree, thanks!
– TomáÅ¡ Pečený
Jun 7 at 6:48




I agree, thanks!
– TomáÅ¡ Pečený
Jun 7 at 6:48










1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted










From the FAQ:




  • For other platforms, the .tgz file unpacks to a "/usr/local" type hierarchy. For system-wide installation, you can unpack all of the
    files into /usr/local/bin, /usr/local/include, etc.

  • The configuration script /usr/local/bin/icu-config or the similar Makefile include fragment /usr/local/lib/icu/current/Makefile.inc
    can be used in building applications.



To extract the archive's icu/usr/local to /usr/local:



sudo tar zxvf icu4c-61_1-Ubuntu16.04-x64.tgz -C /usr/local ./icu/usr/local --strip-components=4


The tar options:




  • -C /usr/local: to put the extracted files in /usr/local


  • ./icu/usr/local: to extract only the contents of ./icu/usr/local of from the archive (skipping the mostly useless readme.txt)


  • --strip-components=4: to extract the files, but remove the leading 4 components (./icu/usr/local) from the paths, since we're already extracting to /usr/local.

If you have used pkg-config before, icu-config seems to be a similar script.






share|improve this answer





















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1044305%2fhow-to-connect-icu-library-with-gcc-in-the-ubuntu-16-04%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote



    accepted










    From the FAQ:




    • For other platforms, the .tgz file unpacks to a "/usr/local" type hierarchy. For system-wide installation, you can unpack all of the
      files into /usr/local/bin, /usr/local/include, etc.

    • The configuration script /usr/local/bin/icu-config or the similar Makefile include fragment /usr/local/lib/icu/current/Makefile.inc
      can be used in building applications.



    To extract the archive's icu/usr/local to /usr/local:



    sudo tar zxvf icu4c-61_1-Ubuntu16.04-x64.tgz -C /usr/local ./icu/usr/local --strip-components=4


    The tar options:




    • -C /usr/local: to put the extracted files in /usr/local


    • ./icu/usr/local: to extract only the contents of ./icu/usr/local of from the archive (skipping the mostly useless readme.txt)


    • --strip-components=4: to extract the files, but remove the leading 4 components (./icu/usr/local) from the paths, since we're already extracting to /usr/local.

    If you have used pkg-config before, icu-config seems to be a similar script.






    share|improve this answer

























      up vote
      2
      down vote



      accepted










      From the FAQ:




      • For other platforms, the .tgz file unpacks to a "/usr/local" type hierarchy. For system-wide installation, you can unpack all of the
        files into /usr/local/bin, /usr/local/include, etc.

      • The configuration script /usr/local/bin/icu-config or the similar Makefile include fragment /usr/local/lib/icu/current/Makefile.inc
        can be used in building applications.



      To extract the archive's icu/usr/local to /usr/local:



      sudo tar zxvf icu4c-61_1-Ubuntu16.04-x64.tgz -C /usr/local ./icu/usr/local --strip-components=4


      The tar options:




      • -C /usr/local: to put the extracted files in /usr/local


      • ./icu/usr/local: to extract only the contents of ./icu/usr/local of from the archive (skipping the mostly useless readme.txt)


      • --strip-components=4: to extract the files, but remove the leading 4 components (./icu/usr/local) from the paths, since we're already extracting to /usr/local.

      If you have used pkg-config before, icu-config seems to be a similar script.






      share|improve this answer























        up vote
        2
        down vote



        accepted







        up vote
        2
        down vote



        accepted






        From the FAQ:




        • For other platforms, the .tgz file unpacks to a "/usr/local" type hierarchy. For system-wide installation, you can unpack all of the
          files into /usr/local/bin, /usr/local/include, etc.

        • The configuration script /usr/local/bin/icu-config or the similar Makefile include fragment /usr/local/lib/icu/current/Makefile.inc
          can be used in building applications.



        To extract the archive's icu/usr/local to /usr/local:



        sudo tar zxvf icu4c-61_1-Ubuntu16.04-x64.tgz -C /usr/local ./icu/usr/local --strip-components=4


        The tar options:




        • -C /usr/local: to put the extracted files in /usr/local


        • ./icu/usr/local: to extract only the contents of ./icu/usr/local of from the archive (skipping the mostly useless readme.txt)


        • --strip-components=4: to extract the files, but remove the leading 4 components (./icu/usr/local) from the paths, since we're already extracting to /usr/local.

        If you have used pkg-config before, icu-config seems to be a similar script.






        share|improve this answer













        From the FAQ:




        • For other platforms, the .tgz file unpacks to a "/usr/local" type hierarchy. For system-wide installation, you can unpack all of the
          files into /usr/local/bin, /usr/local/include, etc.

        • The configuration script /usr/local/bin/icu-config or the similar Makefile include fragment /usr/local/lib/icu/current/Makefile.inc
          can be used in building applications.



        To extract the archive's icu/usr/local to /usr/local:



        sudo tar zxvf icu4c-61_1-Ubuntu16.04-x64.tgz -C /usr/local ./icu/usr/local --strip-components=4


        The tar options:




        • -C /usr/local: to put the extracted files in /usr/local


        • ./icu/usr/local: to extract only the contents of ./icu/usr/local of from the archive (skipping the mostly useless readme.txt)


        • --strip-components=4: to extract the files, but remove the leading 4 components (./icu/usr/local) from the paths, since we're already extracting to /usr/local.

        If you have used pkg-config before, icu-config seems to be a similar script.







        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered Jun 7 at 7:12









        muru

        128k19269459




        128k19269459






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1044305%2fhow-to-connect-icu-library-with-gcc-in-the-ubuntu-16-04%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            Which professions warranted travel in Medieval times?

            How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

            Trouble downloading packages list due to a “Hash sum mismatch” error