Could Pale Moon be compiled in VS2017?
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Could Pale Moon be compiled in VS2017?
Could Pale Moon be compiled in VS2017 environment?
-
- Fanatic
- Posts: 126
- Joined: 2014-05-04, 14:00
- Location: United States
Re: Could Pale Moon be compiled in VS2017?
To my knowledge - No, Pale Moon 27 requires Visual Studio 2013 on Windows and nothing else.
1911 remains the service pistol for all ages!
"Speak softly and carry a big stick; you will go far." — Theodore Roosevelt
"Speak softly and carry a big stick; you will go far." — Theodore Roosevelt
-
- Pale Moon guru
- Posts: 35640
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Could Pale Moon be compiled in VS2017?
Allrecent updates of Visual Studio have breaking changes at the code level. Even though there is an open issue to see what would be needed to VS2017 the code as it is will simply only compile on exactly VS2013 and if moved to a different version in the future, it will also be exclusive to thatversion only.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite