mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lin Yuan <apefor...@gmail.com>
Subject Re: MXNet developer setup on Mac with VSCode for develop, test and debug
Date Fri, 20 Jul 2018 15:57:11 GMT
Pedro, I have tried CLion briefly but found it could not resolve C++ tags
by default and throwing many errors/warning. Did you set any thing extra?
Besides, debugging in a mixed language (Python and C++) environment, you
don't have to switch between IDEs in VSCode.

On Thu, Jul 19, 2018 at 9:59 AM Pedro Larroy <pedro.larroy.lists@gmail.com>
wrote:

> Have you guys tried CLion, works like a charm for me. (Requires license).
>
> On Wed, Jul 18, 2018 at 10:09 PM Naveen Swamy <mnnaveen@gmail.com> wrote:
>
> > Thanks Sandeep for putting this together, it would make it easy for
> people
> > who prefer to IDEs to get started with MXNet easily.
> >
> > On Wed, Jul 18, 2018 at 1:04 PM, Lin Yuan <apeforest@gmail.com> wrote:
> >
> > > Hi Aaron,
> > >
> > > This doc is for development on Mac. It is not intended for Windows
> users.
> > > Maybe we can start a different thread to discuss about MXNet build on
> > > Windows? I have tried it myself on a GPU instances built on Windows
> DLAMI
> > > 10.0. I would love to share with you my setup steps.
> > >
> > > Lin
> > >
> > > On Wed, Jul 18, 2018 at 11:43 AM Markham, Aaron
> > > <markhama@amazon.com.invalid>
> > > wrote:
> > >
> > > > This is tangential, but Lin, I noticed during the RC1 tests you said
> > you
> > > > tried it out on Windows and it worked for you. I'd like to get VS2017
> > or
> > > VS
> > > > Code working, take Sandeep's setup content and possibly your Windows
> > > > experience, and improve the MXNet Windows setup guide. I've tried it
> > and
> > > > failed. Multiple times. I also tried the MKLDNN instructions and
> > failed.
> > > I
> > > > tried the setup tools batch file and was hit with a lot of dependency
> > > > errors. Some of the problem isn't in the MXNet docs, but in the
> > > > dependencies' documentation, but I'm left to go figure that out on my
> > > own.
> > > > Anyway, any help you can provide here would be great. Also, if any of
> > you
> > > > reading this has a sort of checklist or guide for Windows, I'd love
> to
> > > see
> > > > it.
> > > >
> > > > BTW, I'm using Windows 10 with an NVIDIA GeForce GTX 980, and was
> > trying
> > > > to use VS2017 Community Edition and MKL. I went to MKL after OpenBLAS
> > > > wasn't installing/building.
> > > >
> > > > ´╗┐On 7/18/18, 10:59 AM, "Lin Yuan" <apeforest@gmail.com> wrote:
> > > >
> > > >     Thanks for the well-written document! As a new MXNet developer, I
> > > have
> > > >     found it very helpful.
> > > >
> > > >     Lin
> > > >
> > > >     On Wed, Jul 18, 2018 at 10:50 AM sandeep krishnamurthy <
> > > skm@apache.org
> > > > >
> > > >     wrote:
> > > >
> > > >     > Hello Community,
> > > >     >
> > > >     >
> > > >     >
> > > >     > As a MXNet contributor, I had issues and took me some time on
> > > getting
> > > >     > hands-on with MXNet codebase, being able to code, test, DEBUG
> > > > python/CPP
> > > >     > combination. I have documented the steps for MXNet development
> > > setup
> > > > using
> > > >     > VSCode on Mac. Document starts from installing all required
> > > >     > tools/packages/IDEs/extensions and then provides steps for
> > > debugging
> > > > mix of
> > > >     > Python/CPP code, which is most likely the case for any MXNet
> > > > developer, all
> > > >     > in single IDE window. By end of this document, anyone should
be
> > > able
> > > > to
> > > >     > walk through the MXNet code, debug and be able to make first
> code
> > > > change.
> > > >     >
> > > >     >
> > > >     >
> > > >     > Please feel free to add comments, make changes as necessary.
> > > >     >
> > > >     >
> > > >     >
> > > > https://cwiki.apache.org/confluence/display/MXNET/
> > > MXNet+Developer+Setup+on+Mac
> > > >     >
> > > >     > Best,
> > > >     > Sandeep
> > > >     >
> > > >
> > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message