Community
    • Login

    Help to porting SourceCookifier for 64bit

    Scheduled Pinned Locked Moved Notepad++ & Plugin Development
    18 Posts 6 Posters 4.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Meta ChuhM
      Meta Chuh moderator @Ekopalypse
      last edited by

      @Ekopalypse

      i guess the easiest thing for the op would be if you upload and publish your sourcecookifier x64 unicode test build. eg at your github repo (binary only) or anywhere else.

      EkopalypseE 1 Reply Last reply Reply Quote 0
      • EkopalypseE
        Ekopalypse @Meta Chuh
        last edited by

        @Meta-Chuh

        but that would bring me into a position which I don’t really like,
        namely doing some kind of maintenance - it is not really python :-D

        1 Reply Last reply Reply Quote 1
        • Alan KilbornA
          Alan Kilborn
          last edited by

          @Meta-Chuh said:

          upload and publish your sourcecookifier x64 unicode test build. eg at your github repo (binary only)

          @Ekopalypse said:

          but that would bring me into a position which I don’t really like, namely doing some kind of maintenance

          Why bin only? One presumes the (source) code fork is already there. And there are plenty of “dead” forks around (so why would you feel obligated to do maintenance).

          EkopalypseE 1 Reply Last reply Reply Quote 2
          • EkopalypseE
            Ekopalypse @Alan Kilborn
            last edited by

            @Alan-Kilborn

            but if you upload something and offer a solution you will be automatically
            the primary person to contact if something doesn’t work as expected as you have
            provided that plugin/source code.

            Alan KilbornA 1 Reply Last reply Reply Quote 0
            • Alan KilbornA
              Alan Kilborn @Ekopalypse
              last edited by

              @Ekopalypse

              Ha. Nah. All you did was fork something and play around with it. Plenty of examples of people doing that on github. Only if you go so far as to take real ownership do you get into the situation you talk about. :)

              1 Reply Last reply Reply Quote 0
              • Michael VincentM
                Michael Vincent
                last edited by

                @Ekopalypse

                Agree - that’s what I’ve been doing with un-maintained N++ plugins. Fork, it improve for me and post if others want it. I don’t plan on trying to include it in the nppPluginList which I think would be the real “taking ownership” thing.

                Alan KilbornA 1 Reply Last reply Reply Quote 2
                • Alan KilbornA
                  Alan Kilborn @Michael Vincent
                  last edited by Alan Kilborn

                  @Michael-Vincent said:

                  …include it in the nppPluginList which I think would be the real “taking ownership” thing.

                  Well, you could go that far if you wanted to, and (I’d say) if you got the original author’s permission…but it is up to you.

                  Downside to not doing this: How would others know about the existence of these plugins (the “column” one especially I look forward to trying out).

                  1 Reply Last reply Reply Quote 1
                  • Michael VincentM
                    Michael Vincent
                    last edited by

                    @Ekopalypse What version of the Microsoft SDK are you using to compile? Is it version 7? What version of Visual Studio Community?

                    I’m using VS Comm 2017 and version 10 of the SDK (v10.0A). I’m getting weird errors and overflows when trying to run the successfully build DLL in N++. Wondering if the supplied DLL in DLLExport are geared for an older version of Visual Studio and / or SDK?

                    1 Reply Last reply Reply Quote 2
                    • Michael VincentM
                      Michael Vincent
                      last edited by

                      More troubling, the same set of tools / versions on Windows 7 actually works for me - my successful build actually runs in N++ without crashing it. But copy that good DLL to Windows 10 and save errors. I wonder if there’s a redistributable that I have on Windows 7 and not on 10? I just don’t know/ understand C#.

                      EkopalypseE 1 Reply Last reply Reply Quote 2
                      • EkopalypseE
                        Ekopalypse @Michael Vincent
                        last edited by

                        @Michael-Vincent

                        Yes, I’m using Win7 as well and I was using VS 2017 community edition and SDK 7.
                        Unfortunately I don’t have Win10 - so cannot confirm your findings.

                        1 Reply Last reply Reply Quote 1
                        • Michael VincentM
                          Michael Vincent @ArkadiuszMichalski
                          last edited by

                          @ArkadiuszMichalski said in Help to porting SourceCookifier for 64bit:

                          Could anyone try port the SourceCookifier plugin for the 64-bit version of Notepad ++?

                          Seems the (perhaps) original author finally got around to it:

                          https://github.com/notepad-plus-plus/nppPluginList/commit/4233a0171213201fc296906200d179b3ace63179

                          Cheers.

                          1 Reply Last reply Reply Quote 2
                          • First post
                            Last post
                          The Community of users of the Notepad++ text editor.
                          Powered by NodeBB | Contributors